Nach ausgeworfen hat webpack.config.js ich mein Eckige Projekt mit dem Befehl kompilieren: npm läuft baut in letzter Zeit, während die Build startete ich folgende Fehlermeldung bekommen:Angular 4 - ASP.Net Kern - Kompilieren Fehler
ERROR in ./node_modules/@angular/http/@angular/http.es5.js
Module not found: Error: Can't resolve 'rxjs/operator/share'
in 'C:\...\[email protected]\c [email protected]'
@ ./node_modules/@angular/core/@angular/core.es5.js 9:0-44
@ ./ClientApp/main.ts @ multi ./ClientApp/main.ts
Module Versionen sind als nächste:
@angular/cli: 1.4.9 (e)
node: 6.11.3
os: win32 x64
@angular/animations: 4.4.6
@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/platform-browser: 4.4.6
@angular/platform-browser-dynamic: 4.4.6
@angular/router: 4.4.6
@angular/cli: 1.4.9
@angular/compiler-cli: 4.4.6
@angular/language-service: 4.4.6
@ngtools/webpack: 1.7.4
typescript: 2.7.0-dev.20171031
und hier ist das NPM-Debug-Log:
info it worked if it ends with ok
verbose cli [ 'C:\\Program Files\\nodejs\\node.exe', verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', verbose cli 'run', verbose cli 'build' ]
info using [email protected]
info using [email protected]
verbose run-script [ 'prebuild', 'build', 'postbuild' ]
info lifecycle [email protected]~prebuild: [email protected]
silly lifecycle [email protected]~prebuild: no script for prebuild, continuing
info lifecycle [email protected]~build: [email protected]
verbose lifecycle [email protected]~build: unsafe-perm in lifecycle true
verbose lifecycle [email protected]~build: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;..............etc ......
verbose lifecycle [email protected]~build: CWD: C:\MyApp
silly lifecycle [email protected]~build: Args: [ '/d /s /c', 'webpack' ]
silly lifecycle [email protected]~build: Returned: code: 2 signal: null
info lifecycle [email protected]~build: Failed to exec build script
verbose stack Error: [email protected] build: `webpack` verbose stack Exit status 2 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16) verbose stack at emitTwo (events.js:106:13) verbose stack at EventEmitter.emit (events.js:191:7) verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14) verbose stack at emitTwo (events.js:106:13) verbose stack at ChildProcess.emit (events.js:191:7) verbose stack at maybeClose (internal/child_process.js:920:16) verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
verbose pkgid [email protected]
verbose cwd C:\MyApp
error Windows_NT 10.0.14393
error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
error node v6.11.3
error npm v3.10.10
error code ELIFECYCLE
error [email protected] build: `webpack` error Exit status 2
error Failed at the [email protected] build script 'webpack'.
error Make sure you have the latest version of node.js and npm installed. error If you do, this is most likely a problem with the ng2-asp-core package, error not with npm itself. error Tell the author that this fails on your system: error webpack error You can get information on how to open an issue for this project with: error npm bugs ng2-asp-core error Or if that isn't available, you can get their info via: error npm owner ls ng2-asp-core error There is likely additional logging output above.
verbose exit [ 1, true ]
Da das Debug-Protokoll auf das ng2-asp-core-Paket als Fehlerquelle zeigt, habe ich den Befehl npm Besitzer ls ng2-asp-core ausgeführt, um den Besitzer zu bekommen, aber bekam einen 404 Fehler: ng2-asp-core 'ist nicht in der npm Registry^
Update: Package.json Datei:
{
"name": "ng2-asp-core",
"version": "0.0.0",
"license": "MIT",
"scripts": {
"ng": "ng",
"start": "webpack-dev-server --port=4200",
"build": "webpack",
"test": "karma start ./karma.conf.js",
"lint": "ng lint",
"e2e": "protractor ./protractor.conf.js",
"pree2e": "webdriver-manager update --standalone false --gecko false --quiet"
},
"private": true,
"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",
"core-js": "^2.4.1",
"rxjs": "^5.4.2",
"zone.js": "^0.8.14",
"lodash": "^4.17.4"
},
"devDependencies": {
"@angular/cli": "1.4.9",
"@angular/compiler-cli": "^4.2.4",
"@angular/language-service": "^4.2.4",
"@ngtools/webpack": "^1.7.4",
"@types/jasmine": "~2.5.53",
"@types/jasminewd2": "~2.0.2",
"@types/lodash": "^4.14.66",
"@types/node": "~6.0.60",
"autoprefixer": "^6.5.3",
"circular-dependency-plugin": "^3.0.0",
"codelyzer": "~3.2.0",
"copy-webpack-plugin": "^4.1.1",
"css-loader": "^0.28.1",
"cssnano": "^3.10.0",
"exports-loader": "^0.6.3",
"file-loader": "^1.1.5",
"html-webpack-plugin": "^2.29.0",
"istanbul-instrumenter-loader": "^2.0.0",
"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",
"less-loader": "^4.0.5",
"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.2",
"webpack": "~3.7.1",
"webpack-concat-plugin": "1.4.0",
"webpack-dev-server": "~2.7.1",
"concurrently": "^3.2.0",
"lite-server": "^2.2.2"
}
}
run npm install rxjs, der Fehler tritt immer noch auf. –
Was ist der Fehler ... –
Fehlgeschlagen bei dem [email protected] Build-Skript 'webpack', wie zuvor –