There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: excludePackageNames: excludePackageNames should be inside a packageRule only

Howdy. I've been using your package to help authenticate a CI publisher tool (sort of like the one you link to from your README). However, I've been running into authentication issues.

When I run npm config get registry with no registry configured in my global ~/.npmrc file, or in a local file, I get: https://registry.npmjs.org/

Taking a look at https://github.com/bahmutov/npm-utils/blob/master/src/set-auth-token.js#L35, it seems only http URLs can be parsed.

Therefore setAuthToken can't remove https, leaving the https in the registry URL in ~/.npmrc.

Therefore my ~/.npmrc file contains https://registry.npmjs.org/:_authToken=${NPM_TOKEN}.

npm does not recognize that line when accessing the registry.npmjs.org registry.

Therefore it does not authenticate.

To install dependencies.

For example as an additional list of command line flags. This will allow to save installed package, etc.

npm.install({
  name: 'foo',
  flags: ['--save']
})

When installing copi, I got this error:

npm WARN deprecated [email protected]: use cross-spawn or cross-spawn-async instead.

Just FYI :-)

To remove unwanted files

And if npm test fails, make sure there is meaningful output

Measure as shown in http://glebbahmutov.com/blog/smaller-published-NPM-modules/

Which should read last commit message and if it contains "TAG:" should publish under that tag

• bahmutov/simple-commit-message#1
• https://medium.com/greenkeeper-blog/one-simple-trick-for-javascript-package-maintainers-to-avoid-breaking-their-user-s-software-and-to-6edf06dc5617#.6yjw2gttx

This should replace npm publish in the script command "semantic-release": "semantic-release pre && npm publish && semantic-release post" command

Should not look for it in the input folder

npm pack <folder> creates .tgz file for publishing

And run it

Tired of gt test runner, use Mocha

If the environment has NPM_TOKEN this command should add token to the registry
(maybe default or take name as argument?). Thus anyone who wants to use private modules
from the public registry can do

npm i npm-utils
$(npm bin)/set-auth-token-var-name

which should produce in file .npmrc

//registry.npmjs.org/:_authToken=${NPM_TOKEN}

and then you can do npm install to install all deps

Puts npm token there

to clean dependencies on commit?

What are they doing for so long?!

npm install <folder> according to npm help install

For some reason, see https://api.travis-ci.org/jobs/147542135/log.txt?deansi=true

[travis-after-all] Failed to parse JSON from "https://api.travis-ci.org/jobs/147542135".

registry-url.js only retrieves the value of registry, which means that it will always append the _authToken to the value of registry. Therefore, scoped registries in the .npmrc configuration file, such as @company:registry, are not supported.

In my use case I have an .npmrc configuration file with two registries in it:

registry = "internal mirror of public registry"
@company:registry = "private registry"

The project's package.json file has set publishConfig to publish to the scoped, @company, registry. The project's name is @company/something.

In my case, I believe the value of the environment variable NPM_TOKEN needs to be appended to @company:registry instead of registry to allow proper authentication when publishing the project.

If you have access to the project's name, you can call something like registry-url to get the appropriate scoped registry.

An example of how registry-url is used can be seen in package-json.

for setting specific version like using npm version 2.0.0

To allow filtering the output

For given npm package, find the repo url, then clone it and run npm install inside

Looks weird when printing this for npm.pack for example

spawning test process npm [ 'pack', '/Users/kensho/git/charts-lib/node_modules/express' ]

Hi Gleb,

I'm not 100% sure, but there is a change that I've faced a small issue in your repo. Please follow the discussion here: https://gitlab.com/hyper-expanse/semantic-release-gitlab/issues/9

To summarise, it seems that npm-utils ignores registry from publishConfig in package.json and authenticates in a wrong repo. This happens when semantic-release-gitlab is trying to publish a release.

How relevant could this be to npm-utils? Or should your lib just be used somehow else in the situation mentioned?

Cheers,
Alex

Update readme references to .npmrc. Explain that it now looks for a local file first before defaulting to ~/.npmrc.

Related: #39

Look how kensho/ng-describe is setup

The merge of pull request #27 removes src/registry-url.js but the file is still used in src/index.js

So when I try to use v1.7.0 I get the error:

Error: Cannot find module './registry-url'
    at Function.Module._resolveFilename (module.js:325:15)
    at Function.Module._load (module.js:276:25)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (...\node_modules\npm-utils\src\index.js:7:16)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)

I am using https://github.com/bahmutov/ci-publish/issues/10 for my gitlab CI process and it depend of npm-utils.

Is there a way to publish public scoped package ? https://www.npmjs.com/docs/orgs/publishing-an-org-scoped-package.html#publishing-a-public-scoped-package

should run npm publish with maybe arguments?

if there are multiple archives, it messes up. Should look at name?

I'm filing this issue on behalf of a report filed against npm-publish-git-tag - https://gitlab.com/hyper-expanse/npm-publish-git-tag/issues/3

There's a minor typo introduced in the following commit - f193b40

require('/npm-prune') should be require('./npm-prune')

local-or-home-npmrc sets the value for node in the engines property of their package.json file to node 6.

Yarn will fail during the installation process if the value of the engines property does not match against the version of Node used to run Yarn - yarnpkg/rfcs#69 (comment)

Therefore, npm-utils, version 1.x, was working for Node 4 Yarn users until local-or-home-npmrc was introduced in version 1.13.0, but now npm-utils, though more specifically local-or-home-npmrc, can't be installed.

I ran into this yesterday when I upgraded my Yarn lockfile, and ran my build (which runs against all supported versions of Node, npm, and Yarn) - https://gitlab.com/hyper-expanse/semantic-release-gitlab-notifier/-/jobs/22286197

error [email protected]: The engine "node" is incompatible with this module. Expected version ">=6".
error Found incompatible module

I'll probably consider locking down the npm-utils version in my project's package.json file as a temporary way to work around the issue.

However, as I still support all Node LTS versions, including Node 4, I'll need to consider a longer-term solution (I do want my downstream consumers to benefit from the features you've been adding to npm-utils, but still be able to use Node 4 is that happens to be their current situation)

Do you have any thoughts, or suggestions, on the matter?

and add badges

For greater flexibility

List of names, like npm.installAll('foo', '[email protected]')

if the caller has .npmrc file with custom registry, the npm-utils.registryUrl is called from node_modules folder - returning the global NPM url.

Probably should execute in the caller's working dir?

Really powerful command, including git commit, tag, etc. See npm help version.
Can set specific version or increment individual number

npm version [<newversion> | major | minor | patch ...]