How to fix npm repository, when Validation Error occurs? - node.js

I encountered a problem when building a project with angular.
To build, I use:
npm install
To run, I use:
npm install
I'm getting an error:
ERROR in ./node_modules/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0 Module build failed: Validation Error
URL Loader Invalid Options
options['name'] should NOT have additional properties options.limit should be number
# ./node_modules/css-loader?{"sourceMap":false,"importLoaders":1}!./node_modules/postcss-loader?{"ident":"postcss"}!./node_modules/font-awesome/css/font-awesome.min.css 6:412-465 # ./node_modules/font-awesome/css/font-awesome.min.css # multi (webpack)-dev-server/client?http://localhost:4200 ./node_modules/bootstrap/dist/css/bootstrap.min.css ./node_modules/font-awesome/css/font-awesome.min.css ./node_modules/quill/dist/quill.snow.css ./src/styles.scss
ERROR in ./node_modules/font-awesome/fonts/fontawesome-webfont.woff?v=4.7.0 Module build failed: Validation Error
URL Loader Invalid Options
options['name'] should NOT have additional properties options.limit should be number
# ./node_modules/css-loader?{"sourceMap":false,"importLoaders":1}!./node_modules/postcss-loader?{"ident":"postcss"}!./node_modules/font-awesome/css/font-awesome.min.css 6:495-547 # ./node_modules/font-awesome/css/font-awesome.min.css # multi (webpack)-dev-server/client?http://localhost:4200 ./node_modules/bootstrap/dist/css/bootstrap.min.css ./node_modules/font-awesome/css/font-awesome.min.css ./node_modules/quill/dist/quill.snow.css ./src/styles.scss
ERROR in ./node_modules/font-awesome/fonts/fontawesome-webfont.ttf?v=4.7.0 Module build failed: Validation Error
URL Loader Invalid Options
options['name'] should NOT have additional properties options.limit should be number
# ./node_modules/css-loader?{"sourceMap":false,"importLoaders":1}!./node_modules/postcss-loader?{"ident":"postcss"}!./node_modules/font-awesome/css/font-awesome.min.css 6:576-627 # ./node_modules/font-awesome/css/font-awesome.min.css # multi (webpack)-dev-server/client?http://localhost:4200 ./node_modules/bootstrap/dist/css/bootstrap.min.css ./node_modules/font-awesome/css/font-awesome.min.css ./node_modules/quill/dist/quill.snow.css ./src/styles.scss
I tried buid this on Windows 10, and on Ubuntu 18.04.
npm -v
6.4.1
node -v
v10.14.2
dependencies stored in package.json:
"dependencies": {
"#angular/animations": "4.2.4",
"#angular/common": "4.2.4",
"#angular/compiler": "4.2.4",
"#angular/core": "4.2.4",
"#angular/forms": "4.2.4",
"#angular/http": "4.2.4",
"#angular/platform-browser": "4.2.4",
"#angular/platform-browser-dynamic": "4.2.4",
"#angular/router": "4.2.4",
"#types/uuid": "3.4.4",
"blueimp-load-image": "2.18.0",
"bootstrap": "4.0.0-beta.3",
"core-js": "2.4.1",
"exif-js": "2.3.0",
"file-saver": "1.3.3",
"font-awesome": "4.7.0",
"jquery": "3.2.1",
"mydatepicker": "2.6.1",
"ngx-quill": "1.6.0",
"popper.js": "1.12.5",
"rxjs": "5.4.2",
"tether": "1.4.0",
"zone.js": "0.8.14"
},
"devDependencies": {
"#angular/cli": "1.4.5",
"#angular/compiler-cli": "4.2.4",
"#angular/language-service": "4.2.4",
"#types/node": "^6.14.2",
"autoprefixer": "6.5.3",
"circular-dependency-plugin": "3.0.0",
"codelyzer": "~3.2.0",
"copy-webpack-plugin": "4.0.1",
"css-loader": "0.28.1",
"cssnano": "3.10.0",
"exports-loader": "0.6.3",
"file-loader": "0.10.0",
"html-webpack-plugin": "2.29.0",
"istanbul-instrumenter-loader": "2.0.0",
"less-loader": "4.0.5",
"license-webpack-plugin": "1.1.1",
"postcss-loader": "1.3.3",
"postcss-url": "5.1.2",
"protractor": "~5.1.2",
"raw-loader": "0.5.1",
"sass-loader": "6.0.3",
"source-map-loader": "0.2.0",
"style-loader": "0.13.1",
"stylus-loader": "3.0.1",
"ts-node": "~3.2.0",
"tslint": "~5.7.0",
"typescript": "~2.3.3",
"url-loader": "0.6.0",
"webpack": "~3.6.0",
"webpack-concat-plugin": "1.4.0",
"webpack-dev-server": "~2.7.1"
}
Probably some of these libraries are not used, but I do not want to delete them. Should I update some of them?

An error occurred during building and I did not see it. The error was connected with old version with font-awesome.

Related

Error: Data path "" must NOT have additional properties(allowedCommonJsDependencies) when upgrading from Angular 11 to 12

So I just updated the Angular version of my project from 11 to 12 and whenever I try to run the server, I get the following error:
Warning: Running a server with --disable-host-check is a security risk. See https://medium.com/webpack/webpack-dev-server-middleware-security-issues-1489d950874a for more information.
"BuildCustomWebpackBrowserSchema" schema is using the keyword "id" which its support is deprecated. Use "$id" for schema ID.
Schema validation failed with the following errors:
Data path "" must NOT have additional properties(allowedCommonJsDependencies).
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! smart-med#0.0.0 start: `node --max_old_space_size=8048 ./node_modules/#angular/cli/bin/ng serve --disable-host-check "pharmacy"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the smart-med#0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
I have already tried deleting node_modules and package_lock-json and run npm i but it didn't work. Furthermore the file "allowedCommonJsDependencies" does not exist on angular.json
Package.json:
"dependencies": {
"#angular/animations": "~12.2.17",
"#angular/cdk": "~12.2.13",
"#angular/cli": "^12.2.18",
"#angular/common": "~12.2.17",
"#angular/compiler": "~12.2.17",
"#angular/core": "~12.2.17",
"#angular/forms": "~12.2.17",
"#angular/localize": "^12.2.17",
"#angular/material": "~12.2.13",
"#angular/material-moment-adapter": "~12.2.13",
"#angular/platform-browser": "~12.2.17",
"#angular/platform-browser-dynamic": "~12.2.17",
"#angular/router": "~12.2.17",
"#angular/service-worker": "~12.2.17",
"#auth0/angular-jwt": "^3.0.1",
"#auth0/auth0-spa-js": "^1.6.0",
"#devexpress/analytics-core": "^21.1.5",
"#ngx-translate/core": "^11.0.1",
"#ngx-translate/http-loader": "^4.0.0",
"#ngxs/logger-plugin": "^3.4.3",
"#ngxs/router-plugin": "^3.4.3",
"#ngxs/store": "^3.4.3",
"#zxing/ngx-scanner": "^3.0.0",
"adal-angular4": "4.0.12",
"angular-tree-component": "~8.5.6",
"angularx-qrcode": "^2.3.7",
"bootstrap": "^3.4.1",
"core-js": "~3.6.4",
"devexpress-reporting-angular": "^21.1.5",
"devextreme": "^21.1.5",
"immer": "^2.0.0",
"keycloak-angular": "^7.3.1",
"keycloak-js": "^10.0.2",
"lodash-es": "^4.17.11",
"lodash.memoize": "^4.1.2",
"moment-timezone": "^0.5.23",
"ngx-infinite-scroll": "^9.0.0",
"ngx-mask": "^9.1.0",
"ngx-responsive": "^9.0.0",
"roboto-fontface": "^0.8.0",
"rxjs": "~6.5.4",
"tslib": "^2.0.0",
"zone.js": "~0.11.4"
},
"devDependencies": {
"#angular-builders/custom-webpack": "~9.0.0",
"#angular-builders/jest": "~9.0.0",
"#angular-devkit/build-angular": "~12.2.18",
"#angular-devkit/build-ng-packagr": "~0.1002.4",
"#angular-devkit/schematics": "~12.2.18",
"#angular/compiler-cli": "~12.2.17",
"#angular/language-service": "~12.2.17",
"#babel/compat-data": "~7.9.0",
"#openapitools/openapi-generator-cli": "^2.2.3",
"#testing-library/angular": "^10.0.2",
"#testing-library/dom": "^7.24.3",
"#testing-library/jest-dom": "^5.11.4",
"#testing-library/user-event": "^12.1.6",
"#types/jasmine": "~2.8.8",
"#types/jasminewd2": "~2.0.3",
"#types/jest": "~25.1.5",
"#types/lodash-es": "^4.17.3",
"#types/moment-timezone": "^0.5.12",
"#types/node": "^12.11.1",
"codelyzer": "^5.1.2",
"http-server": "~0.12.1",
"husky": "^8.0.1",
"istanbul-combine": "^0.3.0",
"jasmine-core": "~3.5.0",
"jasmine-spec-reporter": "~5.0.0",
"jest": "~25.2.7",
"jest-junit": "^10.0.0",
"lint-staged": "^10.2.11",
"ng-packagr": "^12.2.7",
"npm-run-all": "^4.1.5",
"prettier-stylelint": "^0.4.2",
"protractor": "~7.0.0",
"rimraf": "^2.6.3",
"scss-bundle": "^2.5.1",
"stylelint": "^9.10.1",
"stylelint-config-prettier": "^6.0.0",
"stylelint-config-standard": "^18.2.0",
"ts-loader": "^5.4.4",
"ts-node": "~7.0.0",
"tslint": "~6.1.0",
"tslint-plugin-prettier": "^2.0.1",
"typescript": "~4.3.5",
"webpack-bundle-analyzer": "^3.6.0",
"yamljs": "^0.3.0",
"yargs": "^17.1.0"
},
"husky": {
"hooks": {
"pre-commit": "lint-staged"
}
}
How can I fix this?

npm start stop with exit status 3 : Failed to exec start script [Angular]

I'm new on Angular and I have to work on a project in this technology.I set up the project but when I run the npm start command, the process npm start stop suddenly : the ng serve fails. I tried to investigate but I found nothing that can fix my problem.
You can see the errors here : errors
npm version : 6.14.11
node version : v14.15.5
Dependencies in the package.json file :
"dependencies": {
"#angular/animations": "^11.0.3",
"#angular/cdk": "^11.0.1",
"#angular/common": "~11.0.3",
"#angular/compiler": "~11.0.3",
"#angular/core": "~11.0.3",
"#angular/flex-layout": "^11.0.0-beta.33",
"#angular/forms": "~11.0.3",
"#angular/material": "^11.0.1",
"#angular/platform-browser": "~11.0.3",
"#angular/platform-browser-dynamic": "~11.0.3",
"#angular/platform-server": "~11.0.3",
"#angular/router": "~11.0.3",
"#angular/service-worker": "^11.0.3",
"#ngx-prism/core": "^2.0.1",
"#syncfusion/ej2-angular-richtexteditor": "^18.3.52",
"#types/prismjs": "^1.16.2",
"#types/socket.io-client": "^1.4.34",
"angular-http-server": "^1.9.0",
"app-root-path": "^3.0.0",
"chart.js": "^2.9.4",
"compodoc": "0.0.41",
"core-js": "^3.8.0",
"dotenv": "^8.2.0",
"http-server": "^0.12.3",
"http-status": "^1.5.0",
"jquery": "^3.5.1",
"ngx-captcha": "^8.0.1",
"ngx-countdown": "^11.0.0",
"ngx-countdown-timer": "^0.2.0",
"ngx-drag-drop": "^2.0.0",
"ngx-json-viewer": "^2.4.0",
"ngx-mat-select-search": "^3.1.4",
"ngx-pipes": "^2.7.5",
"ngx-socket-io": "^3.2.0",
"prismjs": "^1.22.0",
"rxjs": "^6.6.3",
"rxjs-compat": "^6.6.3",
"socket.io-client": "^3.0.3",
"xls": "^0.5.1",
"xlsx": "^0.16.9",
"zone.js": "^0.11.3"
},
"devDependencies": {
"#angular-devkit/build-angular": "^0.1100.3",
"#angular/compiler-cli": "^11.0.3",
"#compodoc/compodoc": "^1.1.11",
"#types/chart.js": "^2.9.28",
"#types/jasmine": "3.6.2",
"#types/node": "^14.14.10",
"#types/source-map": "^0.5.7",
"#types/webpack": "^4.41.25",
"typescript": "~4.0.0"
}
Do you have an idea ?
I tried to run :
npm cache clean --force
npm install
npm start
But that don't help me.

Angular 10 Warning: Entry point 'devextreme-angular..' contains deep import into module

I'm trying to build my angular app but I'm receiving this kind of warnings:
Warning: Entry point 'devextreme-angular/ui/data-grid' contains deep imports into '{path to node modules}/node_modules/devextreme/ui/data_grid', '{path to node modules}/node_modules/devextreme/bundles/dx.all', '{path to node modules}/node_modules/devextreme/ui/filter_builder', '{path to node modules}/node_modules/devextreme/ui/form', '{path to node modules}/node_modules/devextreme/ui/popup'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Then I have this error:
Generating ES5 bundles for differential loading...
An unhandled exception occurred: Call retries were exceeded
These are my node and angular versions:
Angular CLI: 10.2.1
Node: 12.18.3
OS: win32 x64
Angular: 10.2.4
In the produced log file I have:
[error] Error: Call retries were exceeded
at ChildProcessWorker.initialize ({path to node modules}\node_modules\jest-worker\build\workers\ChildProcessWorker.js:193:21)
at ChildProcessWorker._onExit ({path to node modules}\node_modules\jest-worker\build\workers\ChildProcessWorker.js:274:12)
at ChildProcess.emit (events.js:315:20)
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
This is the package.json file:
"dependencies": {
"#angular/animations": "^10.2.3",
"#angular/cdk": "^10.2.7",
"#angular/common": "^10.2.3",
"#angular/compiler": "^10.2.3",
"#angular/core": "^10.2.3",
"#angular/forms": "^10.2.3",
"#angular/material": "^10.2.7",
"#angular/material-moment-adapter": "^10.2.7",
"#angular/platform-browser": "^10.2.3",
"#angular/platform-browser-dynamic": "^10.2.3",
"#angular/platform-server": "^10.2.3",
"#angular/pwa": "^0.7.1",
"#angular/router": "^10.2.3",
"#angular/service-worker": "^10.2.3",
"#ngx-translate/core": "^11.0.1",
"#ngx-translate/http-loader": "^4.0.0",
"#syncfusion/ej2-angular-richtexteditor": "^18.3.52",
"#tinymce/tinymce-angular": "^4.1.0",
"ajv": "^6.9.1",
"angular-oauth2-oidc": "^10.0.0",
"cdk-table-exporter": "^9.0.2",
"chalk": "^3.0.0",
"classlist.js": "^1.1.20150312",
"core-js": "^2.5.4",
"devexpress-diagram": "^1.0.17",
"devexpress-gantt": "^1.0.10",
"devextreme": "^20.2.3",
"devextreme-angular": "20.2.3",
"font-awesome": "^4.7.0",
"hammerjs": "^2.0.8",
"jquery": "^3.3.1",
"mat-table-exporter": "^9.0.2",
"moment": "^2.24.0",
"node": "^12.18.3",
"node-sass": "^4.9.2",
"popper.js": "^1.14.7",
"rxjs": "^6.5.5",
"rxjs-compat": "^6.0.0",
"tslib": "^1.10.0",
"web-animations-js": "^2.3.1",
"zone.js": "^0.10.3"
},
"devDependencies": {
"#angular-devkit/build-angular": "^0.1002.0",
"#angular-devkit/core": "^10.2.0",
"#angular-devkit/schematics": "^10.2.0",
"#angular/cli": "^10.2.0",
"#angular/compiler-cli": "^10.2.3",
"#angular/language-service": "^10.2.3",
"#types/jasmine": "~2.8.8",
"#types/jasminewd2": "~2.0.3",
"#types/node": "~8.9.4",
"codelyzer": "~6.0.1",
"devextreme-cli": "1.2.4",
"jasmine-core": "~2.99.1",
"jasmine-spec-reporter": "~4.2.1",
"json-server": "^0.12.1",
"karma": "~3.1.1",
"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.9.6"
}
The build works fine on another machine with the same file. I can only think of something wrong in my node and angular/cli versions. I've already deleted node_modules folder and npm cache clean -f

JHipster Application produces message "this.driver.matchesElement" in dev mode

I have a problem running a JHipster application in Dev. Some developers run smoothly, in others the message "TypeError: this.driver.matchesElement is not a function" is displayed. All computers have the same versions of NPM, Yarn, and Node.
Node Version: 8.11.0
NPM Version: 5.6.0
Yarn Version: 1.7.0
Front-End Application StackTrace:
ERROR TypeError: this.driver.matchesElement is not a function
at TransitionAnimationEngine.processLeaveNode (browser.js?881a:3023)
at TransitionAnimationEngine.flush (browser.js?881a:3059)
at InjectableAnimationEngine.AnimationEngine.flush (browser.js?881a:3896)
at eval (animations.js?063e:363)
at ZoneDelegate.invoke (zone.js?6524:388)
at Zone.run (zone.js?6524:138)
at NgZone.runOutsideAngular (core.js?593e:4681)
at AnimationRendererFactory.end (animations.js?063e:361)
at DebugRendererFactory2.end (core.js?593e:15096)
at ViewRef_.detectChanges (core.js?593e:11563)
defaultErrorLogger
Package.json:
{
...
"cacheDirectories": [
"node_modules"
],
"dependencies": {
"#angular/animations": "^6.0.4",
"#angular/common": "5.2.0",
"#angular/compiler": "5.2.0",
"#angular/core": "5.2.0",
"#angular/forms": "5.2.0",
"#angular/platform-browser": "5.2.0",
"#angular/platform-browser-dynamic": "5.2.0",
"#angular/router": "5.2.0",
"#ng-bootstrap/ng-bootstrap": "1.0.0",
"bootstrap": "4.0.0",
"core-js": "2.4.1",
"font-awesome": "4.7.0",
"jquery": "3.2.1",
"ng-jhipster": "0.4.0",
"ngx-cookie": "2.0.1",
"ngx-infinite-scroll": "0.5.1",
"ngx-webstorage": "2.0.1",
"primeng": "5.2.7",
"reflect-metadata": "0.1.10",
"rxjs": "5.5.6",
"swagger-ui": "2.2.10",
"tether": "1.4.0",
"zone.js": "0.8.19",
"ngx-image-cropper": "0.2.8"
},
"devDependencies": {
"#angular/cli": "1.6.6",
"#angular/compiler-cli": "5.2.0",
"#ngtools/webpack": "1.8.5",
"#types/fullcalendar": "3.8.0",
"#types/jasmine": "2.5.53",
"#types/node": "8.0.18",
"#types/quill": "^1.3.3",
"angular2-template-loader": "0.6.2",
"awesome-typescript-loader": "3.2.2",
"browser-sync": "2.18.13",
"browser-sync-webpack-plugin": "1.2.0",
"codelyzer": "4.0.1",
"copy-webpack-plugin": "4.2.3",
"css-loader": "0.28.4",
"exports-loader": "0.6.4",
"extract-text-webpack-plugin": "3.0.2",
"file-loader": "1.1.5",
"fullcalendar": "3.9.0",
"generator-jhipster": "4.14.4",
"html-loader": "0.5.0",
"html-webpack-plugin": "2.30.1",
"jasmine-core": "2.7.0",
"karma": "1.7.1",
"karma-chrome-launcher": "2.2.0",
"karma-coverage": "1.1.1",
"karma-intl-shim": "1.0.3",
"karma-jasmine": "1.1.0",
"karma-junit-reporter": "1.2.0",
"karma-notify-reporter": "1.0.1",
"karma-phantomjs-launcher": "1.0.4",
"karma-remap-istanbul": "0.6.0",
"karma-sourcemap-loader": "0.3.7",
"karma-webpack": "2.0.4",
"merge-jsons-webpack-plugin": "1.0.11",
"phantomjs-prebuilt": "2.1.16",
"proxy-middleware": "0.15.0",
"quill": "^1.3.2",
"rimraf": "2.6.1",
"source-map": "0.6.1",
"sourcemap-istanbul-instrumenter-loader": "0.2.0",
"style-loader": "0.18.2",
"to-string-loader": "1.1.5",
"tslint": "5.5.0",
"tslint-loader": "3.5.3",
"typescript": "2.6.2",
"uglifyjs-webpack-plugin": "1.1.5",
"web-app-manifest-loader": "0.1.1",
"webpack": "3.10.0",
"webpack-dev-server": "2.9.5",
"webpack-merge": "4.1.1",
"webpack-notifier": "1.5.1",
"webpack-visualizer-plugin": "0.1.11",
"workbox-webpack-plugin": "3.0.0-beta.1",
"write-file-webpack-plugin": "4.1.0",
"xml2js": "0.4.17"
},
"engines": {
"node": ">=6.9.0"
},
...
}
Thanks.
So we had an issue where the system.js file was defining the version to use but the package.json file was getting the most up to date version. This was causing an issue on the front end.
After we removed the version from system.js then it was happy.
This was a problem with version 6.0.4 of angular animations. I updated the project to version 6.0.6 and corrected all dependency warnings. It is now working properly

Cannot find type definition file for 'node'

I am getting strange errors after updating angular, webpack and typescript.
Any idea what I could be missing?
When I run the app with npm start I get the following errors:
[at-loader] Cannot find type definition file for 'hammerjs'.
[at-loader] Cannot find type definition file for 'node'.
[at-loader] src\app\app.component.ts:26:14
Cannot find name 'require'.
[at-loader] src\app\app.component.ts:30:15
Cannot find name 'require'.
Here are the dependencies:
"dependencies": {
"#angular/common": "2.4.4",
"#angular/compiler": "2.4.4",
"#angular/core": "2.4.4",
"#angular/forms": "2.4.4",
"#angular/http": "2.4.4",
"#angular/material": "2.0.0-beta.1",
"#angular/platform-browser": "2.4.4",
"#angular/platform-browser-dynamic": "2.4.4",
"#angular/platform-server": "2.4.4",
"#angular/router": "3.4.4",
"#angularclass/conventions-loader": "^1.0.13",
"#angularclass/hmr": "~1.2.2",
"#angularclass/hmr-loader": "~3.0.2",
"#ng-bootstrap/ng-bootstrap": "1.0.0-alpha.18",
"angular2-jwt": "0.1.28",
"angular2-moment": "1.1.0",
"auth0-lock": "10.10.1",
"bootstrap": "4.0.0-alpha.5",
"cky-meta": "^1.0.2",
"core-js": "^2.4.1",
"hammerjs": "2.0.8",
"http-server": "^0.9.0",
"ie-shim": "^0.1.0",
"intl": "^1.2.5",
"ng2-img-cropper": "0.7.7",
"ng2-page-scroll": "3.2.1",
"ng2-sharebuttons": "1.1.5",
"reflect-metadata": "^0.1.9",
"rxjs": "5.0.3",
"web-animations-js": "2.2.2",
"zone.js": "0.7.6"
},
"devDependencies": {
"#angular/compiler-cli": "~2.4.4",
"#types/chai": "3.4.34",
"#types/core-js": "^0.9.35",
"#types/es6-shim": "^0.31.32",
"#types/hammerjs": "^2.0.33",
"#types/jasmine": "^2.5.41",
"#types/node": "^6.0.60",
"#types/protractor": "^4.0.0",
"#types/selenium-webdriver": "2.53.39",
"#types/source-map": "^0.5.0",
"#types/uglify-js": "^2.0.27",
"#types/webpack": "^2.2.2",
"add-asset-html-webpack-plugin": "^1.0.2",
"angular-router-loader": "^0.5.0",
"angular2-template-loader": "^0.6.0",
"assets-webpack-plugin": "^3.5.1",
"awesome-typescript-loader": "~3.0.0-beta.18",
"bootstrap-loader": "2.0.0-beta.19",
"codelyzer": "~2.0.0-beta.4",
"copy-webpack-plugin": "^4.0.0",
"css-loader": "^0.26.0",
"exports-loader": "^0.6.3",
"expose-loader": "^0.7.1",
"file-loader": "^0.9.0",
"gh-pages": "^0.12.0",
"html-webpack-plugin": "^2.26.0",
"imports-loader": "^0.7.0",
"istanbul-instrumenter-loader": "1.2.0",
"jasmine-core": "^2.5.2",
"json-loader": "^0.5.4",
"karma": "^1.4.0",
"karma-chrome-launcher": "^2.0.0",
"karma-coverage": "^1.1.1",
"karma-jasmine": "^1.0.2",
"karma-mocha-reporter": "^2.2.2",
"karma-remap-coverage": "^0.1.4",
"karma-sourcemap-loader": "^0.3.7",
"karma-webpack": "2.0.1",
"ng2-facebook-sdk": "1.2.0",
"ngc-webpack": "^1.1.2",
"node-sass": "4.3.0",
"npm-run-all": "^4.0.1",
"parse5": "^3.0.1",
"postcss-loader": "1.2.2",
"protractor": "^4.0.14",
"raw-loader": "0.5.1",
"resolve-url-loader": "1.6.1",
"rimraf": "~2.5.4",
"sass-loader": "4.1.1",
"script-ext-html-webpack-plugin": "^1.5.0",
"source-map-loader": "^0.1.6",
"string-replace-loader": "^1.0.5",
"style-loader": "^0.13.1",
"to-string-loader": "^1.1.5",
"ts-helpers": "1.1.2",
"ts-node": "^2.0.0",
"tslint": "4.3.1",
"typedoc": "^0.5.5",
"typescript": "2.1.5",
"typings": "2.1.0",
"url-loader": "^0.5.7",
"v8-lazy-parse-webpack-plugin": "^0.3.0",
"webpack": "2.2.0",
"webpack-dev-middleware": "^1.9.0",
"webpack-dev-server": "2.2.0",
"webpack-dll-bundles-plugin": "^1.0.0-beta.5",
"webpack-md5-hash": "^0.0.5",
"webpack-merge": "~2.4.0"
},
"engines": {
"node": ">= 4.2.1",
"npm": ">= 3"
}
Try re-importing the #types/node package by running this in the Package Manager Console in Visual Studio:
npm i -D #types/node
If a specific version must be used, you can specify:
npm i -D #types/node#6.0.10
That seems more likely to be a problem of versions within the typings.json file. Can you try the following?
typings install dt~node --save
typings install dt~core-js --save
typings install dt~hammerjs --save
It could either be a mismatched ts-node version in which updating ts-node should fix it found here or it could be an incorrect tsconfig.json found here
If these don't work here are some links you may find useful:
https://github.com/shlomiassaf/angular2-modal/issues/213
VS2015: "Cannot find type definition" and "File not found" errors
In my case, after doing an npm update I was getting this error. It disappeared by restarting my node server :
npm start
You might need to apply multiple solutions to solve this issue!
STEP 1
You might need to install missing typings from #types
it's already present and still you are getting this error proceed to step 2
STEP 2
If you are using ts-loader you will need to upgrade this
STEP 3 (Not applicable to all)
In some cases it's the webpack versioning which causes this error; upgrading to webpack version, ts-node, awesome-typescript-loader etc will solve it for you
STEP 4 (Angular only)
If you have used core-js upgrade its version
In general solution varies for all however its the node modules version where you will need to play around a bit! It's more of hit and try
All the best!

Resources