Npm ERR! enoent and is related to npm not being able to find a file.įor some reason, npm is trying to install moduleA for coolApp, even though it doesn't need to directly, and also, it is using the relative path string as it is literally specified in the package.json file for moduleB, even though that isn't valid for coolApp since it is in a relatively different location. This package.json is used by all projects in the workspace, including the initial application project that is created by the CLI when it creates the workspace. The CLI command ng new creates a package.json file when it creates the new workspace. Npm ERR! enoent This is most likely not a problem with npm itself Both npm and yarn install the packages that are identified in a package.json file. Npm ERR! enoent ENOENT, open '/src/node/apps/moduleA' Here are some of the more important ones to be aware of. npm install (from git) npm install (with options) In addition to arguments, npm install can be run with different options. Instead, the dependencies are hoisted to the root directory's nodemodules folder. Npm ERR! addLocal Could not install /src/node/apps/moduleA npm install WILL NOT generate a new nodemodules folder inside the sub-directory. Now if I try to npm install : cd /src/modules/moduleA Npm install doesn't seem to work if I depend on a local package that itself depends on another local package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |