Related
I'm trying to remove unused packages from the package.json files for a few projects but I'm running into issues with peer dependencies. There are some tools, such as depcheck, which try to list all of the "unused" packages, but it doesn't differentiate between actual unused packages, and packages that are unused because they're peer dependencies.
Is there a package out there, or some npm command I'm not familiar with, that will allow me to either list all peer dependencies in my project or, at the very least, allow me to type in a package name and see if that package is installed because it's a peer dependency of another package?
For posterity, here's an example of just the dependencies for one of my projects. In this project, I know for instance that reflect-metadata is a peer dependency of #nestjs/common, but I only discovered that after uninstalling it.
"dependencies": {
"#google-cloud/storage": "^3.2.1",
"#google-cloud/vision": "^1.3.0",
"#google/maps": "^0.5.5",
"#nestjs/common": "^6.6.7",
"#nestjs/core": "^6.6.7",
"#nestjs/platform-express": "^6.6.7",
"#slack/webhook": "^5.0.1",
"#typeform/api-client": "^1.5.1",
"algoliasearch": "^3.34.0",
"array-uniq": "^2.1.0",
"basic-auth": "^2.0.1",
"child-process-promise": "^2.2.1",
"class-transformer": "^0.2.3",
"class-validator": "^0.10.0",
"express": "^4.17.1",
"firebase-admin": "^8.5.0",
"firebase-functions": "^3.2.0",
"geoip-lite": "^1.3.8",
"geolib": "^3.0.4",
"glob": "^7.1.4",
"hbs": "^4.0.4",
"hubspot-api": "^2.2.10",
"json2csv": "^4.5.3",
"lodash": "^4.17.15",
"luxon": "^1.17.2",
"node-fetch": "^2.6.0",
"postmark": "^2.2.9",
"promise-settle": "^0.3.0",
"qrcode": "^1.4.1",
"redux": "^4.0.4",
"reflect-metadata": "^0.1.13",
"rxjs": "^6.5.3",
"sales-tax": "^2.0.10",
"sanitize-filename": "^1.6.3",
"sharp": "^0.23.0",
"stripe": "^7.9.0"
},
This is a great question, not sure why it was downvoted.
Unfortunately I don't know of an existing, nicely automated way to do this.
You can test an individual package like so:
npm uninstall some-package && npm ls
If there are any peer dependency violations, they will be printed out and the command will exit nonzero.
So you could combine this with the output of one of the other tools mentioned, iterate through the candidates for orphaned packages, remove them one-by-one, and test the output between each change. Then do an npm uninstall --save to commit the ones that didn't produce an error, or npm install to roll back the ones that do. This could be automated, but I will leave that as an exercise to the reader.
check-peer-deps
Verifies that the peerDependency requirements of all top level dependencies are satisfied.
Installation
You can install this on your system with:
npm i -g check-peer-deps
Please note that this utility requires npm to be available.
Usage
Simply change into the directory of the project you wish to check the peerDependencies of and run the program.
cd foobar
check-peer-deps
If the minimum versions of all your top level peerDependencies are satisfied then there will be no output, otherwise you will see something similar to this:
check-peer-deps A dependency satisfying eslint-config-airbnb-base's peerDependency of 'eslint#^4.9.0' was not found! Current: eslint#^4.6.0 Package dependencies can satisfy the peerDependency? Yes
This tells you that eslint-config-airbnb-base is requiring eslint#^4.9.0 as a peerDependency, but the project currently only specifies eslint#^4.6.0, allowing a potential issue to arise if eslint#4.6.0 was installed and not updated before installing. The output also tells you that although the minimum allowed version is too low, the maximum allowed version does satisfy the peerDependencies requirement.
install-peers-cli
CLI to install project's peerDependencies, without side effects. Works with npm, yarn. Supports yarn workspaces flow.
Install
yarn
$ yarn add --dev install-peers-cli
npm
$ npm install --save-dev install-peers-cli
Usage
Add package.json script:
{
"scripts": {
"install-peers": "install-peers"
}
}
Then run yarn install-peers (or npm run install-peers) to install peer dependencies of your project. It won't update lock files or modify package.json, keeping your setup pure and clean. Any other lifecycle script could be used depending on your use case.
You still may see "unmet peer dependency" warnings during regular install phase, due to installation flow of npm/yarn.
There will be a file called package-lock.json after once you do npm install.
By analyzing package-lock.json file, you can understand the dependencies of each package.
For more details this blog can be referred.
Dependencies of a package are required for the correct running of the package.
But there are some optional dependencies, which can be skipped.
You can use --no-optional argument while installing so these extra packages will not be installed.
But make sure your application is working fine without these optional packages.
This question already has answers here:
Angular 6 - Could not find module "#angular-devkit/build-angular"
(47 answers)
Closed 8 months ago.
I tried to update the angular CLI following this, but now I can't run my app. When I try to run the command ng serve, it gives me this error:
Could not find the implementation for builder #angular-devkit/build-angular:dev-server
Error: Could not find the implementation for builder #angular-devkit/build-angular:dev-server
at WorkspaceNodeModulesArchitectHost.resolveBuilder (C:\Users\Lupus\Documents\full-stack-projects\financial-app-ui\node_modules\#angular\cli\node_modules\#angular-devkit\architect\node\node-modules-architect-host.js:49:19)
at ServeCommand.initialize (C:\Users\Lupus\Documents\full-stack-projects\financial-app-ui\node_modules\#angular\cli\models\architect-command.js:135:55)
at process._tickCallback (internal/process/next_tick.js:68:7)
at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
I have tried everything I could found.
I tried to manually install devkit with the command npm install --save-dev #angular-devkit/build-angular
I tried to run the command npm i --only=dev
I tried to run the commands
:
npm install
ng update
npm update
Removed the node_modules folder and the package-lock.json file and ran the commands all again.
Nothing worked. Running ng v gives me this:
Angular CLI: 8.0.3
Node: 10.15.0
OS: win32 x64
Angular: 8.0.1
... animations, cdk, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
-----------------------------------------------------------
#angular-devkit/architect 0.13.9
#angular-devkit/build-angular 0.13.9
#angular-devkit/build-optimizer 0.13.9
#angular-devkit/build-webpack 0.13.9
#angular-devkit/core 7.3.9
#angular-devkit/schematics 8.0.3
#angular/cli 8.0.3
#ngtools/webpack 7.3.9
#schematics/angular 8.0.3
#schematics/update 0.800.3
rxjs 6.5.2
typescript 3.4.5
webpack 4.29.0
And my package.json is like this:
{
"name": "financial-app-ui",
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e"
},
"private": true,
"dependencies": {
"#angular/animations": "^8.0.1",
"#angular/cdk": "^8.0.1",
"#angular/common": "^8.0.1",
"#angular/compiler": "^8.0.1",
"#angular/core": "^8.0.1",
"#angular/forms": "^8.0.1",
"#angular/platform-browser": "^8.0.1",
"#angular/platform-browser-dynamic": "^8.0.1",
"#angular/router": "^8.0.1",
"core-js": "^2.6.9",
"font-awesome": "^4.7.0",
"primeicons": "^1.0.0",
"primeng": "^7.1.3",
"rxjs": "~6.5.2",
"tslib": "^1.10.0",
"zone.js": "~0.9.1"
},
"devDependencies": {
"#angular-devkit/build-angular": "^0.13.9",
"#angular/cli": "^8.0.3",
"#angular/compiler-cli": "^8.0.1",
"#angular/language-service": "^8.0.1",
"#types/jasmine": "~2.8.8",
"#types/jasminewd2": "~2.0.3",
"#types/node": "~8.9.4",
"codelyzer": "~4.5.0",
"jasmine-core": "~2.99.1",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~4.0.0",
"karma-chrome-launcher": "~2.2.0",
"karma-coverage-istanbul-reporter": "~2.0.1",
"karma-jasmine": "~1.1.2",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~5.4.0",
"ts-node": "~7.0.0",
"tslint": "~5.11.0",
"typescript": "~3.4.5"
}
}
Does anyone have any other suggestion?
I got this working by reinstalling the build-angular package. Note the '--save-dev' flag on the install command:
npm uninstall #angular-devkit/build-angular
npm install --save-dev #angular-devkit/build-angular
Resolved my issue by using the below command:
ng update #angular/cli #angular/core --allow-dirty --force
I had the same problem. Just two command solved my problem
npm uninstall #angular-devkit/build-angular
npm install --save-dev #angular-devkit/build-angular
//OR
npm install #angular-devkit/build-angular
If this doesn't work. don't worry. run this command.
ng update #angular/cli #angular/core --allow-dirty --force
I was able to solve this problem by installing the package #angular-devkit/build-angular using this command:
npm install #angular-devkit/build-angular --force
ng update should have updated the version for your #angular-devkit/build-angular
I ran into this as well and what I did was created a new Angular app and ensured that ng serve was working fine for that newly created Angular app. I then copied and used the following from the working Angular app's package.json, which is:
`"#angular-devkit/build-angular": "~0.802.2",`
Ensure you run npm install
(The version would most probably change with each Angular update - so check what version you need to use by following the steps I have outlined - if ng update doesn't already update it for you)
Make sure you have this configuration in your angular.json
"serve": {
"builder": "#angular-devkit/build-angular:dev-server",
"options": {
"browserTarget": "angular8:build"
},
"configurations": {
"production": {
"browserTarget": "angular8:build:production"
}
}
}
And make sure you have installed this package
#angular-devkit/build-angular
I'm having the same issue, but in my case I am trying to serve a downloaded template of an Angular project. At first it gave me this error after a ng serve --open terminal command.
An unhandled exception occurred:
Could not find module "#angular-devkit/build-angular" from "D:\WORK\Desarrollo\plantillas descargadas\argon-dashboard-angular-master".
I solved that following this Stack Overflow question: https://stackoverflow.com/a/50333128,
but got these warnings:
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN #ngtools/webpack#7.3.1 requires a peer of #angular/compiler-cli#>=5.0.0
<8.0.0 || ^7.0.0-beta.0 but none is installed. You must install peer dependencies
yourself.
npm WARN ajv-keywords#3.4.1 requires a peer of ajv#^6.9.1 but none is installed. You
must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.9
(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents#1.2.9: wanted {"os":"darwin","arch":"any"} (current:
{"os":"win32","arch":"x64"})
But then I got this error after trying the command:
ng serve --open
An unhandled exception occurred: Could not find the implementation for builder
#angular-devkit/build-angular:dev-server
I noticed that there were some files missing in my node_modules folder, probably caused by my current connection speed. Anyway I tried on a different computer, somewhere else, opened a clone of the project itself and ran the command:
npm update
then take the project in a .rar file to my working computer and decompressed it, run my VS Code and it just worked perfectly.
In angular.json change this line "builder": "#angular-builders/build-angular:browser", to "builder": "#angular-devkit/build-angular:browser", solved my problem.
Since you got this error, you might be using an app which uses old version of angular dev such as 0.6.x
If you simply uninstall and reinstall , it's very likely that you got other errors like "cannot find module '#angular/compiler-cli/src/tooling'" or Cannot find module '#angular/compiler-cli/ngcc' because it seems that angular has been making a lot changes.
If you solved the problem simply by updating , then forget about the following.
It's best to use the next version(relative to 0.6.5) that doesn't cause the build error and ngcc error.
In my case, the correct version is between the build error and ngcc error.
This worked for me.
First run update command ie. ng update
On running this you may get a list of other packages that should also be updated.
Install these packages manually as suggested.
After this on running ng serve I got error in angular.json for missing tsconfig.app.json file. These I added manually from this link . I also added tsconfig.spec.json file.
That is it, I ran ng serve again and the project complied successfully.
If you have npm 7+ installed in your machine try this command in terminal:
npm install --legacy-peer-deps instead of npm install and then run ng serve.
I faced this same issue while running the projects build on older version but none of the solution above could help me. Finally, I found the solution and I am sharing it with you.
Double Check Versions:
I looked at package.json & checked the all versions of all the Angular/Webkit programs, removing the ones giving me errors Typescript errors such as rxjs and googlemaps.
Remove the package-lock.json. Add all the correct versions of Angular, Webkit, Typescript, etc... checking to see what past versions render. This means looking through the Version history for packages on npmjs.com and matching by date / age and version numbers. Make the changes in package.json and save it.
"dependencies" {
"#agm/core": "1.0.0",
"#angular/cdk": "6.1.0",
"rxjs": "6.0.0",
"rxjs-compat": "6.0.0",
...
},
...
"devDependencies": {
"#angular-devkit/build-angular": "0.6.1", // old: "^6.1.0",
"#angular/cli": "6.1.0", // new: "6.1.0",
"#angular/compiler-cli": "6.1.0",
"typescript": "2.7.2"
...
}
Start fresh by removing all the old modules:
rm -fR ./node_modules/#angular; rm -fR ./node_modules/#angular-devkit/; rm -fR ./node_modules/typescript; rm -fR ./node_modules/rxjs*; rm package-lock.json;
Then re-install:
npm install;
.Pug Template Fix: I'm using a .pug loader so I had to manually patch: node_modules/#angular-devkit/build-angular/src/angular-cli-files/models/webpack-configs/common.js to allow Webpack to render Pug files. Add this line after the html rule inside that file:
{ test: /.pug$/, use: [ { loader: "apply-loader" }, { loader: "pug-loader" } ] },.
This is imitating what the ng-add-pug-loader.js file is doing to load .pug files in Angular version 6.
Okay so I'm really more of a designer learning to code. For a project at work I'm helping out with an Angular project so I needed to learn how to use npm and stuff to install Angular CLI and it's deps.
I have an angular project running. It was super easy, no problem. I didn't really edit very much of the package.json, just some of the basics for adding Angular stuff like ng-serve.
When I switched over to our departments actual project, I ran into some pretty big issues getting it to build. Eventually sorted it out, but it kept giving me an error about sass not being able to compile or something to that extent.
Then I moved back over to my practice project. I copy and pasted it into a sub directory of our full project so that I could begin the process of pulling over components that I had made over to the main project. When I tried to run it again, it didn't run! It gave me a whole bunch of errors basically saying that I didn't have node-sass installed. Which I thought I did. It's listed in the dependencies section of the package.json and even after hitting "npm install" a couple of times it was still giving me node-sass errors. When I went back to the original folder that I had copied practice project from it also failed to run even though I'd not changed that file at all.
So then I thought... maybe I removed node-sass as a global install? I remember when I was looking up webpack tutorials after starting my Angular practice project, reading that it's best to do as few global installs as possible because you want each project to have it's own specific version of the dep before you upgrade them etc.
And I remember looking up my global install deps and then looking up how to uninstall one, but I don't remember if I did that for node-sass or not.
Anyway, once I run node-sass install globally on the other project it also starts working no problem.
TL;DR
Do npm depencies install locally?
If they are listed but there is no local or global install, shouldn't npm install install it? Or does it not?
If it does, then how come I have node-sass listed as a dep in the package.json file and running npm install didn't fix it?
Here's my package.json for reference:
{
"name": "spanner-app",
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e"
},
"private": true,
"dependencies": {
"#angular/animations": "^6.0.3",
"#angular/common": "^6.0.3",
"#angular/compiler": "^6.0.3",
"#angular/core": "^6.0.3",
"#angular/forms": "^6.0.3",
"#angular/http": "^6.0.3",
"#angular/platform-browser": "^6.0.3",
"#angular/platform-browser-dynamic": "^6.0.3",
"#angular/router": "^6.0.3",
"core-js": "^2.5.4",
"node-sass": "^4.9.0",
"rxjs": "^6.0.0",
"zone.js": "^0.8.26"
},
"devDependencies": {
"#angular/compiler-cli": "^6.0.3",
"#angular-devkit/build-angular": "~0.6.6",
"typescript": "~2.7.2",
"#angular/cli": "~6.0.7",
"#angular/language-service": "^6.0.3",
"#types/jasmine": "~2.8.6",
"#types/jasminewd2": "~2.0.3",
"#types/node": "~8.9.4",
"codelyzer": "~4.2.1",
"jasmine-core": "~2.99.1",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~1.7.1",
"karma-chrome-launcher": "~2.2.0",
"karma-coverage-istanbul-reporter": "~2.0.0",
"karma-jasmine": "~1.1.1",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~5.3.0",
"ts-node": "~5.0.1",
"tslint": "~5.9.1"
}
}
Thoughts?
dependencies listed in package.json will be installed locally (for the project only) when running npm install. These dependencies will be installed in the node_modules folder by default.
You can check if node-sass is installed for the project by looking for the node-sass folder in node_modules. node-sass will be installed locally by npm install even though it is also installed globally.
You're right that you should have as few packages installed globally as possible, and having a dependency installed globally should only be a last resort temporary solution to your problem. In your situation I would do the following:
Remove node-sass from package.json
Uninstall node-sass globally: npm uninstall -g node-sass
Check if the node_modules/node-sass folder exists
If it does, delete it
Re-install it by npm install --save node-sass
Verify that the issue is fixed
If it's still not working: delete the entire node_modules folder, then run npm install again
VS 2015 community edition (at home), npm 3.10, Angular 2
Im trying to pull get Angular2 setup within an ASP.Net MVC 5 app. The template I started with used an older version of Angular, so I updated the package references.
When I build, the first error in the list is:
Build:Cannot find type definition file for 'node'
There are dozens of other errors after that but Im assuming most are due to this first issue.
Here is the package.json and typings.json
package.json
{
"version": "1.0.0",
"name": "aspnet",
"private": true,
"scripts": {
"postinstall": "typings install",
"typings": "typings"
},
"dependencies": {
"#angular/common": "~4.0.0",
"#angular/compiler": "~4.0.0",
"#angular/core": "~4.0.0",
"#angular/forms": "~4.0.0",
"#angular/http": "~4.0.0",
"#angular/platform-browser": "~4.0.0",
"#angular/platform-browser-dynamic": "~4.0.0",
"#angular/router": "~4.0.0",
"angular-in-memory-web-api": "~0.3.0",
"systemjs": "0.19.40",
"core-js": "^2.4.1",
"rxjs": "5.0.1",
"zone.js": "^0.8.4",
"bootstrap": "^3.3.7"
},
"devDependencies": {
"#types/core-js": "^0.9.41",
"gulp": "^3.9.1",
"gulp-clean": "^0.3.2",
"gulp-concat": "^2.6.1",
"gulp-tsc": "^1.3.1",
"gulp-typescript": "^3.1.6",
"path": "^0.12.7",
"typescript": "~2.1.0",
"typings": "~2.1.1"
}
}
typings.json
{
"globalDependencies": {
"core-js": "registry:dt/core-js#0.0.0+20160725163759",
"jasmine": "registry:dt/jasmine#2.2.0+20160621224255",
"node": "registry:dt/node#6.0.0+20160909174046"
}
}
If I try to update just the typings, I get these messages
*typings WARN deprecated 11/21/2016: "registry:dt/node#6.0.0+20160909174046" is deprecated (updated, replaced or removed)
typings WARN deprecated 9/14/2016: "registry:dt/core-js#0.0.0+20160725163759" is deprecated (updated, replaced or removed)
typings WARN deprecated 10/25/2016: "registry:dt/jasmine#2.2.0+20160621224255" is deprecated (updated, replaced or removed)*
[ update ]
cleaning out my node_modules folder, then running npm install again cleared things up. This seems to happen most often when I move a project folder to another location on my system.
In my case, I solved my problem. Hopefully it helps some else later.
npm install #types/node --save-dev
I had several problems updating packages through visual studio. From now i always update or add packages with the powershell console.
Start PowerShell and navigate to the folder where package.json is located and then run npm install Restart visual studio after the installation is done.
You can also try to delete your node_modules folder then run npm install
Hope this will solve your problems.
Restarting or reloading my VSCode worked
For local Visual Studio
If you're starting with a clean template the build in VS functionality should probably work!
Go to Dependencies > npm > Right Click > Restore Packages
Then try build again.
For Visual Studio Team Services
Install node https://nodejs.org/en/download/
Restart your agent service (VSTS Agent) if not using hosted agents
Add a build task to run npm install
Click the menu icon next to 'Working folder' to choose the location where your project.json file is located.
sometimes its just because some package(s) are missing. you can try running yarn install or npm install should resolve.
The easiest way to go around this in vscode is.
create a .vscode directory, then inside it, create settings.json and put the below json and you are good to go.
{
"search.exclude": {
"**/node_modules": true
},
"files.watcherExclude": {
"**/.git/objects/**": true,
"**/.git/subtree-cache/**": true,
"**/node_modules/**": true,
"env-*": true
},
"files.exclude": {
"**/.git": true,
"**/.DS_Store": true,
"**/node_modules": true,
"env*": true
}
}
Problem can be around other issues as well
Try one of the step of the solution posted here Cannot find type definition file for 'node' by me
I had this problem when i've been working with RN and i put a incorrect dependency on my package.
"#types/": "react-navigation/native",
react-navigation/native don't exists
json
When i tried run tsc with it, i got this
Restart Typescript or re-open vscode worked for me
I have a project with dependencies in package.json. When I install with npm install, I get packages installed in ~/.npm but not in the current folder's node_modules.
NPM is creating node_modules, but not installing packages there. There's a .staging folder within node_modules, which contains all of the packages for the projects, but they're not being moved out after retrieval.
Using Node v6.9.1 / npm v3.10.8.
There aren't any other projects/node_modules installed in directories higher than the current one, though there is a package.json in the parent directory as well. No node_modules directory gets created in the parent directory, however.
Strangely enough, when I manually install a package like npm install #angular/core it installs without problem.
This is on Ubuntu 16.04.
package.json:
{
"name": "",
"version": "0.5.0",
"description": "website (Angular2/NodeJS)",
"main": "main.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "John Halbert <https://halbert.tech> (john#halbert.tech)",
"license": "SEE LICENSE IN LICENSE.md",
"dependencies": {
"#angular/common": "^2.1.1",
"#angular/compiler": "^2.1.1",
"#angular/core": "^2.1.1",
"#angular/forms": "^2.1.1",
"#angular/http": "^2.1.1",
"#angular/platform-browser": "^2.1.1",
"#angular/platform-browser-dynamic": "^2.1.1",
"#angular/router": "^3.1.1",
"core-js": "^2.4.1",
"reflect-metadata": "^0.1.8",
"systemjs": "^0.19.39",
"zone.js": "^0.6.26"
},
"devDependencies": {
"concurrently": "^3.1.0",
"typings": "^1.4.0"
}
}
Try to run
echo "" > $(npm config get userconfig)
npm config edit
To see if you have change de node modules default folder, if so, you can reset the configurations by doing
echo "" > $(npm config get globalconfig)
npm config --global edit
After doing more research it looks like this is a memory issue with my server. Running on a low-end VPS with 128Mb RAM.
There are a few suggestions on how to deal with this. I found others suggesting npm config set jobs 1 as a way to limit memory usage, but this hasn't worked for me. Others suggest adding (more) swap, which is disallowed by my hosting provider.
The npm process is actually being killed so it appears this is likely the culprit.