this error happens to me when I want to do the npm install and it is canceled in the middle of the process, It should be noted that this did not happen before.
I already applied many of the suggestions I saw, for example: disable the anti virus, run as administrator, among others.
version node :10.13.0 and 10.16.0 (nvm)
version angular :8.0.0
error console PowerShell
my dependencies project
"dependencies": {
"#agm/core": "^1.0.0-beta.5",
"#angular-material-components/datetime-picker": "^2.0.3",
"#angular-material-components/moment-adapter": "^2.0.1",
"#angular/animations": "^8.0.0",
"#angular/cdk": "^8.0.0",
"#angular/common": "^8.0.0",
"#angular/compiler": "^8.0.0",
"#angular/core": "^8.0.0",
"#angular/fire": "^5.2.3",
"#angular/flex-layout": "^7.0.0-beta.23",
"#angular/forms": "^8.0.0",
"#angular/http": "^7.2.1",
"#angular/material": "^8.0.0",
"#angular/material-moment-adapter": "^8.0.2",
"#angular/platform-browser": "^8.0.0",
"#angular/platform-browser-dynamic": "^8.0.0",
"#angular/platform-server": "^8.0.0",
"#angular/router": "^8.0.0",
"#auth0/angular-jwt": "^2.1.0",
"#ng-bootstrap/ng-bootstrap": "^4.0.1",
"#ngx-translate/core": "^11.0.1",
"#ngx-translate/http-loader": "^4.0.0",
"#swimlane/ngx-datatable": "^15.0.0",
"#tinymce/tinymce-angular": "^3.5.0",
"#types/lodash": "^4.14.106",
"#types/pdfjs-dist": "~2.0.1",
"amazing-time-picker": "^1.8.0",
"angular-calendar": "^0.27.19",
"angularfire2": "^5.1.1",
"animate.css": "^3.7.0",
"card": "^2.4.0",
"chart.js": "^2.8.0",
"classlist.js": "^1.1.20150312",
"core-js": "^2.6.2",
"css-element-queries": "^1.1.1",
"date-fns": "^1.30.1",
"easy-pie-chart": "^2.1.7",
"file-saver": "^2.0.2",
"firebase": "^5.8.0",
"font-awesome": "4.7.0",
"hammerjs": "^2.0.8",
"intl": "^1.2.5",
"jquery": "^3.3.1",
"moment": "^2.23.0",
"ng-block-ui": "^2.1.0",
"ng-circle-progress": "^1.5.1",
"ng-currency-format": "^0.1.6",
"ng2-charts": "^1.6.0",
"ng2-currency-mask": "^5.3.1",
"ng2-pdf-viewer": "~5.3.4",
"ng2-validation": "^4.2.0",
"ng2modules-easypiechart": "0.0.4",
"ng5-breadcrumb": "0.0.6",
"ngx-device-detector": "1.4.2",
"ngx-mat-select-search": "^1.7.6",
"ngx-perfect-scrollbar": "^7.2.0",
"ngx-slick-carousel": "^0.4.4",
"ngx-spinner": "^7.1.0",
"ngx-toastr": "^9.1.1",
"ngx-tour-core": "4.1.1",
"ngx-tour-md-menu": "4.1.1",
"ngx-tour-ng-bootstrap": "^4.0.1",
"ngx-webcam": "^0.2.5",
"node-sass": "^4.14.1",
"normalize.css": "^8.0.1",
"pdfjs-dist": "2.5.207",
"perfect-scrollbar": "^1.4.0",
"promise-polyfill": "^8.1.0",
"rxjs": "^6.3.3",
"rxjs-compat": "^6.3.3",
"screenfull": "^4.0.0",
"slick-carousel": "^1.8.1",
"sortablejs": "^1.8.1",
"sweetalert2": "^8.19.0",
"ts-helpers": "^1.1.2",
"videogular2": "^6.4.0",
"web-animations-js": "^2.3.1",
"zone.js": "~0.10.2"
},
"devDependencies": {
"#angular-devkit/build-angular": "^0.800.0",
"#angular/cli": "^8.0.0",
"#angular/compiler-cli": "^8.0.0",
"#angular/language-service": "^8.0.0",
"#types/jasmine": "^3.3.7",
"#types/jquery": "^3.3.29",
"#types/node": "^10.12.18",
"#types/systemjs": "^0.20.6",
"#types/webpack-env": "^1.13.7",
"codelyzer": "^4.5.0",
"gulp-sass": "^5.0.0",
"jasmine-core": "^3.3.0",
"jasmine-spec-reporter": "^4.2.1",
"karma": "^4.0.0",
"karma-chrome-launcher": "^2.2.0",
"karma-cli": "^2.0.0",
"karma-coverage-istanbul-reporter": "^2.0.4",
"karma-jasmine": "^2.0.1",
"karma-jasmine-html-reporter": "^1.4.0",
"karma-phantomjs-launcher": "^1.0.4",
"node-sass-magic-importer": "^5.3.2",
"protractor": "^5.4.2",
"rxjs-tslint": "^0.1.6",
"ts-node": "^7.0.1",
"tslint": "^5.12.1",
"typescript": "3.4.5",
"webpack-bundle-analyzer": "^4.5.0"
}
Application Usage
The error might be coming up as it is already in use by another program (without you realising about it, meaning it is running in the background).
To fix this issue, you need to find out which process(es) is/are using the folder. There are multiple methods to do this, and there is a discussion about this here.
You can use the Resource Monitor on Windows 7, 8, 10 and 11, or you can also use PowerShell. There is also an application made by Microsoft in the Sysinternals suite called Process Explorer.
Once you've found the process which is using the folder, you can kill the task. Warning! Do not kill the program if you are unsure of what it is, as it could be a core system file, and ending it may result in irregular behaviour, crashes, and more.
Once you've done that, and the process has been successfully ended, you can run the following command again.
npm install
Hopefully, then, the command should run successfully when the install script changes the folder!
Permission Lack
To fix a permission lack, you need to run the script as an administrator. To do this, run the script in an Administrator Command Prompt or Administrator PowerShell window.
Then, inside of it, run the following command.
npm install
If that doesn't work, you may have to change the permissions of the folder. You can see the instructions here.
Issue:
There is a open issue with latest npm on windows, please check here
Workaround
In the above case eventhough there is no direct dependency of npm, npm getting installed in node modules. So please check package lock file if there is npm in it and the package referring it. If you can correct the package referring npm or downgrading or removing will work.
Install npm#8.3.1 as dev dependency
I would suggest to go with Workaround 1 rather than Workaround 2 as we don't need npm dependency in package as it already been installed globally.
Related
I need to compile and old Angular project with these dependencies:
"dependencies": {
"#angular/animations": "^6.0.9",
"#angular/cdk": "^6.3.3",
"#angular/common": "^6.0.9",
"#angular/compiler": "^6.0.9",
"#angular/core": "^6.0.9",
"#angular/forms": "^6.0.9",
"#angular/http": "^6.0.9",
"#angular/material": "^6.3.3",
"#angular/platform-browser": "^6.0.9",
"#angular/platform-browser-dynamic": "^6.0.9",
"#angular/router": "^6.0.9",
"core-js": "^2.5.7",
"npmlog": "^4.1.2",
"rxjs": "^6.2.2",
"rxjs-compat": "^6.2.2",
"zone.js": "^0.8.26"
},
"devDependencies": {
"#angular-devkit/build-angular": "~0.6.8",
"#angular/cli": "^6.0.8",
"#angular/compiler-cli": "^6.0.8",
"#angular/language-service": "^6.0.9",
"#types/jasmine": "~2.5.53",
"#types/jasminewd2": "~2.0.2",
"codelyzer": "~4.4.2",
"jasmine-core": "~2.6.2",
"jasmine-spec-reporter": "~4.1.0",
"karma": "~1.7.0",
"karma-chrome-launcher": "~2.1.1",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^1.2.1",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
"prettier": "^1.16.4",
"protractor": "^5.3.2",
"ts-node": "~8.0.3",
"tslint": "~5.8.0",
"typescript": "~2.7.2"
}
I'm using Nodejs version 8.9.4 and the npm install command works well; however, when I run ng serve command, I have this message:
ng serve
Node.js version v8.9.4 detected.
The Angular CLI requires a minimum Node.js version of either v12.14 or v14.15.
Please update your Node.js version or visit https://nodejs.org/ for additional instructions.
According to this https://gist.github.com/LayZeeDK/c822cc812f75bb07b7c55d07ba2719b3 table, angular-cli ~6.0.8 works with Nodjs 8.9.4.
But ok, I have installed Nodejs v14.15; ng serve list tons of errors; for example:
$ ng serve
Your global Angular CLI version (12.2.6) is greater than your local version (6.0.8). The local Angular CLI version is used.
To disable this warning use "ng config -g cli.warnings.versionMismatch false".
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
Date: 2022-09-02T09:56:14.497Z
Hash: 39187bc129a2ef15b208
Time: 10705ms
chunk {main} main.js, main.js.map (main) 162 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 250 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 5.22 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 17.1 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 6.53 MB [initial] [rendered]
ERROR in ./src/styles.scss (./node_modules/raw-loader!./node_modules/postcss-loader/lib??embedded!./node_modules/sass-loader/lib/loader.js??ref--14-3!./src/styles.scss)
Module build failed: Error: Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (83)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.12.0
at module.exports (/home/myuser/Desktop/works/dir1/fram1xyz/source/frontend/node_modules/node-sass/lib/binding.js:13:13)
at Object.<anonymous> (/home/myuser/Desktop/works/dir1/fram1xyz/source/frontend/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object.sassLoader (/home/myuser/Desktop/works/dir1/fram1xyz/source/frontend/node_modules/sass-loader/lib/loader.js:24:22)
ERROR in ./src/app/app.component.scss
Module build failed: Error: Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (83)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.12.0
at module.exports (/home/myuser/Desktop/works/dir1/fram1xyz/source/frontend/node_modules/node-sass/lib/binding.js:13:13)
at Object.<anonymous> (/home/myuser/Desktop/works/dir1/fram1xyz/source/frontend/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object.sassLoader (/home/myuser/Desktop/works/dir1/fram1xyz/source/frontend/node_modules/sass-loader/lib/loader.js:24:22)
What I have to do to start the framework?!?
I try to setup a nodejs project called "docdoku-web-front" and i have dependencies problems on bower.
When i try to install my project with the command: npm run dev, i have this errors:
Please note that,
datatables#1.9.4 depends on jquery#~1.8.0 which resolved to jquery#1.8.3
docdokuplm depends on jquery#1.9.1 which resolved to jquery#1.9.1
bootstrap-switch#1.7.0 depends on jquery#~1.9.0 which resolved to jquery#1.9.1
jqueryui#1.9.2 depends on jquery#>= 1.8 which resolved to jquery#1.9.1
selectize#0.12.6 depends on jquery#>=1.7.0 which resolved to jquery#1.9.1
bootstrap-datepicker#1.4.1 depends on jquery#>=1.7.1 which resolved to jquery#1.9.1
bootstrap#3.4.1 depends on jquery#1.9.1 - 3 which resolved to jquery#1.9.1
bootstrap#2.3.2 depends on jquery#>=1.8.0 <2.1.0 which resolved to jquery#1.9.1
jQuery-QueryBuilder#2.0.1 depends on jquery#>= 1.9.0 which resolved to jquery#1.9.1
jquery-extendext#0.1.2 depends on jquery#>=1.9.1 which resolved to jquery#1.9.1
Resort to using jquery#1.9.1 which resolved to jquery#1.9.1
Code incompatibilities may occur.
Please note that,
docdokuplm depends on bootstrap#~2.3.2 which resolved to bootstrap#2.3.2
bootstrap-datepicker#1.4.1 depends on bootstrap#>=2.0.4 <4.0 which resolved to bootstrap#3.4.1
jQuery-QueryBuilder#2.0.1 depends on bootstrap#^3.1.0 which resolved to bootstrap#3.4.1
Resort to using bootstrap#~2.3.2 which resolved to bootstrap#2.3.2
Code incompatibilities may occur.
After investigating, i believe i must change versions on bower.json but i don't know how.
Here is my bower.json
{
"name": "docdokuplm",
"version": "1.1.0",
"dependencies": {
"async": "~0.9.0",
"backbone": "~1.0.0",
"bootbox": "~3.3.0",
"bootstrap": "~2.3.2",
"bootstrap-combobox": "~1.1.6",
"bootstrap-datepicker": "~1.4.1",
"bootstrap-switch": "#1.7.0",
"buzz": "~1.1.4",
"dat.gui": "*",
"datatables": "1.9.4",
"date.format": "~1.2.3",
"fontawesome": "~4.7.0",
"jquery": "#1.9.1",
"jquery-maskedinput": "~1.3.1",
"jQuery-QueryBuilder": "~2.0.1",
"jqueryui": "1.9.2",
"lodash": "~2.4.1",
"modernizr": "~2.7.1",
"moment": "~2.17.1",
"moment-timezone": "~0.5.11",
"mustache": "~0.8.2",
"requirejs": "~2.1.10",
"requirejs-i18n": "~2.0.4",
"requirejs-text": "~2.0.10",
"selectize": "~0.12.0",
"threejs": "https://raw.githubusercontent.com/mrdoob/three.js/r90/build/three.min.js",
"tweenjs": "~16.6.0",
"underscore": "~1.4.2",
"unorm": "1.3.3",
"nvd3": "^1.8.4",
"jwt-decode": "^2.2.0",
"oidc-client": "^1.4.1"
},
"devDependencies": {},
"resolutions": {
"jquery": "1.9.1",
"bootstrap": "~2.3.2"
}
}
Do you have ideas how can i fix it ?
After investigating, i find the solution. My user session have not enough permissions, when i try to install bower manually, i have not permissions on /usr/bin/bower. And i have the same problem with the grunt server. I think i must remove my session and restart setup.
I am working on an Angular 4 project. I have created a project that has certain dependencies. The project in itself works fine.
Now I wish to use this project in another project. I added the former project to package.json (under dependencies) of the latter.
Now when I run npm install, the package gets installed, but its dependencies are not, and I have to install them manually to get my project working.
Can anyone tell me why is this happening? If there are any errors on my part in implementing this?
Code:
ui-common package.json
"dependencies": {
"#angular/cdk": "^2.0.0-beta.11",
"#angular/common": "^4.4.6",
"#angular/compiler": "^4.4.6",
"#angular/core": "^4.4.6",
"#angular/forms": "^4.4.6",
"#angular/http": "^4.4.6",
"#angular/material": "^2.0.0-beta.11",
"#angular/platform-browser": "^4.4.6",
"#angular/platform-browser-dynamic": "^4.4.6",
"#angular/router": "^4.4.6",
"ag-grid": "^17.1.1",
"ag-grid-angular": "^17.1.0",
"angular-split": "=0.2.2",
"angular-tree-component": "^7.0.2-beta1",
"core-js": "=2.5.1",
"draggabilly": "^2.2.0", // The one causing trouble
"foundation-sites": "=6.3.1",
"rxjs": "^5.5.2",
"x2js": "^3.2.1",
"zone.js": "=0.8.18"
}
client-app package.json
"dependencies": {
"#angular/animations": "^4.3.1",
"#angular/cdk": "^2.0.0-beta.11",
"#angular/common": "=4.4.6",
"#angular/compiler": "=4.4.6",
"#angular/core": "=4.4.6",
"#angular/forms": "=4.4.6",
"#angular/http": "=4.4.6",
"#angular/material": "^2.0.0-beta.11",
"#angular/platform-browser": "=4.4.6",
"#angular/platform-browser-dynamic": "=4.4.6",
"#angular/router": "=4.4.6",
"#goldsam/ng-golden-layout": "0.0.3",
"#ngui/scrollable": "^0.9.1",
"#ngui/utils": "^0.8.1",
"ag-grid": "^16.0.1",
"ag-grid-angular": "^16.0.0",
"angular-tree-component": "=7.0.2-beta1",
"core-js": "=2.5.1",
"enhanced-resolve": "=3.4.1",
"foundation-sites": "=6.3.1",
"golden-layout": "^1.5.9",
"intl": "=1.2.5",
"mdn-polyfills": "=5.5.0",
"morgan": "=1.9.0",
"popper.js": "^1.12.9",
"rxjs": "=5.5.2",
"typescript-collections": "1.3.2",
"ui-common": "1.0.0-beta.25", // package included here
"zone.js": "=0.8.18"
}
Have you tried doing npm install --include dependencies. It might also be the fact that you might be running an older version as well so you need to do
npm install -v 2.0.0
This should install the gem dependencies in the Atom project folder
UPDATE:
I performed my upgrade using the manual steps and it worked fine.
Afterwards, I noticed that version 4.3.0 has a new --verbose flag, so I ran it again with the --force flag. It still hangs with no error at yarn run webpack:build.
I then ran yarn webpack:build by itself. It looked like it completed everything, but did not return control to the console. I noticed a yellow message box in my taskbar notification area, that says 'JHipster' Notification Image. When I click on that notification, the job completes and control returns to the console. (I have noticed this notification looks different on Win10 and I don't think it requires a click to dismiss.)
This notification does not appear when running jhipster:upgrade, so I am guessing that is what is hanging up the process.
(original post)
I have generated a jhipster project (4.1.1) and have been working with it. I tried to run jhipster:upgrade to 4.2.0 but the process never completes. (I left it overnight.)
I set up and repeated this process on another computer, and it runs fine.
I have tried to identify why/where the process is hanging on my main computer but have been unsuccessful.
Anyone have some steps, tips to identify what is going wrong?
My environment:
Win7 Enterprise
java version "1.8.0_74"
git version 2.12.0.windows.1
node v6.10.2
yarn 0.21.3
Command output:
C:\applications\jhipster\formsLib>yo jhipster:upgrade
Welcome to the JHipster Upgrade Sub-Generator
This will upgrade your current application codebase to the latest JHipster version
Looking for latest generator-jhipster version...
New generator-jhipster version found: 4.2.0
Git repository detected
Updating generator-jhipster to 4.2.0 . This might take some time...
Several node processes kick off and run for a while, but then they go idle.
I have tried uninstalling and reinstalling node and yarn.
I enabled NODE_DEBUG=cluster,net,http,fs,tls,module,timers node and reran it. The last few lines before it stalls are:
NET 15272: _read
NET 15272: onread 21
NET 15272: got data
NET 15272: _read
NET 15272: onread 33
NET 15272: got data
NET 15272: _read
NET 15272: onread 73
NET 15272: got data
NET 15272: _read
process 15272 is node "C:\Users\mbaxley\AppData\Local\Yarn\config\global\node_modules\.bin\\..\yo\lib\cli.js" jhipster:upgrade
View Remaining Node Tasks
The only file updated during the process is the package.json file. Here is the diff of the modified file:
diff --git a/package.json b/package.json
index 7a2a6b8..eb7de34 100644
--- a/package.json
+++ b/package.json
## -16,11 +16,11 ##
"#angular/platform-browser-dynamic": "2.4.9",
"#angular/router": "3.4.9",
"#ng-bootstrap/ng-bootstrap": "1.0.0-alpha.21",
+ "angular2-cookie": "1.2.6",
"angular2-infinite-scroll": "0.3.4",
"bootstrap": "4.0.0-alpha.6",
- "font-awesome": "4.7.0",
- "angular2-cookie": "1.2.6",
"core-js": "2.4.1",
+ "font-awesome": "4.7.0",
"jquery": "3.1.1",
"ng-jhipster": "0.1.9",
"ng2-webstorage": "1.5.1",
## -47,7 +47,7 ##
"exports-loader": "0.6.4",
"extract-text-webpack-plugin": "2.1.0",
"file-loader": "0.10.1",
- "generator-jhipster": "4.1.1",
+ "generator-jhipster": "4.2.0",
"html-loader": "0.4.5",
"html-webpack-plugin": "2.28.0",
"image-webpack-loader": "3.2.0",
## -65,9 +65,12 ##
"lazypipe": "1.0.1",
"lodash": "4.17.4",
"map-stream": "0.0.6",
+ "node-sass": "4.5.0",
"phantomjs-prebuilt": "2.1.14",
+ "postcss-loader": "1.3.0",
"proxy-middleware": "0.15.0",
"run-sequence": "1.2.2",
+ "sass-loader": "5.0.1",
"sourcemap-istanbul-instrumenter-loader": "0.2.0",
"string-replace-webpack-plugin": "0.1.3",
"style-loader": "0.14.0",
## -81,9 +84,6 ##
"webpack-visualizer-plugin": "0.1.11",
"write-file-webpack-plugin": "3.4.2",
"xml2js": "0.4.17",
- "sass-loader": "5.0.1",
- "node-sass": "4.5.0",
- "postcss-loader": "1.3.0",
"yargs": "6.6.0"
},
"engines": {
I am trying to install my npm dependencies on Ubuntu 14.04.3 (Linux ubuntu 3.13.0-45-generic #74-Ubuntu) from package.json file. I don't know if it is important, but Ubuntu is a virtual machine. I install dependencies in /tmp directory so it isn't any shared folder or samba resource.
Node.js version: 0.12.7.
Npm version: 3.3.9.
Package.json:
{
...
"devDependencies": {
"babel-loader": "5.3.*",
"bootstrap": "3.3.*",
"css-loader": "0.19.*",
"del": "2.0.*",
"extract-text-webpack-plugin": "0.8.*",
"file-loader": "0.8.*",
"gulp": "3.9.*",
"gulp-eslint": "1.0.*",
"gulp-util": "3.0.*",
"html-loader": "0.3.*",
"karma": "0.13.*",
"karma-chai-plugins": "0.6.*",
"karma-mocha": "0.2.*",
"karma-phantomjs-launcher": "0.2.*",
"karma-webpack": "1.7.*",
"mocha": "2.3.*",
"phantomjs": "1.9.*",
"style-loader": "0.12.*",
"url-loader": "0.5.*",
"webpack": "1.12.*",
"yargs": "3.27.*"
},
"engines": {
"node": ">= 0.12.0"
}
"dependencies": {
"express": "4.13.*"
}
}
I use --no-bin-links install flag (I need to copy node_modules directory to another NTFS based location).
When i am installing dependencies i have following error:
RangeError: Maximum call stack size exceeded
at emit (events.js:107:17)
at null.<anonymous>(/usr/lib/node_modules/npm/node_modules/npmlog/node_modules/are-we-there-yet/index.js:14:10)
at emit (events.js:107:17)
at null.<anonymous> (/usr/lib/node_modules/npm/node_modules/npmlog/node_modules/are-we-there-yet/index.js:14:10)
at emit (events.js:107:17)
at null.<anonymous> (/usr/lib/node_modules/npm/node_modules/npmlog/node_modules/are-we-there-yet/index.js:14:10)
at emit (events.js:107:17)
at null.<anonymous> (/usr/lib/node_modules/npm/node_modules/npmlog/node_modules/are-we-there-yet/index.js:14:10)
at emit (events.js:107:17)
at TrackerGroup.finish (/usr/lib/node_modules/npm/node_modules/npmlog/node_modules/are-we-there-yet/index.js:60:8)
Does anybody have any idea how to fix it?
You most probabbly experienced NPM Issues #9224 or #9239.
To work around the issues, you can install the packages into /tmp without the --no-bin-links flag and make sure that you replace the symlinks with files/dirs afterwards. You can use rsync -L to copy the files to NTFS with symlinks transformed into referent files and dirs.