You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
[x ] npm is producing incorrect or undesirable behavior.
What's going wrong?
How it should be:
I use npm install underscore.string command to make a local installation in a folder without a package.json file. In theory this should give the following result:
makes a local installation of package and CREATES a package.json file.
What I get:
What I get as a result is this:
makes a global installation of package and DOSEN'T CREATE a package.json file.
I have the same issue with others packages.
How can the CLI team reproduce the problem?
I'm not sure, but: I have the newest version of node.js [8.11.3 LTS] and npm [6.1.0]. And I still get this issue.
Hi, so I tried to reinstall node and npm. It didn't change anything.
The same problem occurs.
'npm config get' command shows the same as before.
Don't know if it's important, but:
The problem occurs only when I try to make a local installation to a a folder without a package.json file.
If I create in this folder package.json file, before I began to install locally a package, then the local installation works. Then the package is only in the folder.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm opening this issue because:
What's going wrong?
How it should be:
I use
npm install underscore.string
command to make a local installation in a folder without a package.json file. In theory this should give the following result:What I get:
What I get as a result is this:
I have the same issue with others packages.
How can the CLI team reproduce the problem?
I'm not sure, but: I have the newest version of node.js [8.11.3 LTS] and npm [6.1.0]. And I still get this issue.
supporting information:
npm -v
prints: 8.11.3node -v
prints: 6.1.0npm config get registry
prints: https://registry.npmjs.org/The text was updated successfully, but these errors were encountered: