Cannot get File Publish to work
See original GitHub issueI can’t seem to get File Publish to build successfully. An ideas? I can’t figure out what comes after this bit to try to resolve it.
** I am using VS 2017
TS7017: Element implicitly has an 'any' type because type 'Icons' has no index signature.
Child extract-text-webpack-plugin:
[0] ./~/css-loader/lib/css-base.js 2.19 kB {0} [built]
[1] ./~/css-loader!./~/bootstrap/dist/css/bootstrap.css 201 kB {0} [built]
[2] ./~/css-loader!./~/font-awesome/css/font-awesome.css 42 kB {0} [built]
[3] ./~/base64-js/index.js 3.48 kB {0} [built]
[4] ./~/buffer/index.js 48.6 kB {0} [built]
[5] ./~/css-loader!./Client/styles/vendor.css 1.97 kB {0} [built]
[6] ./~/font-awesome/fonts/fontawesome-webfont.eot 82 bytes {0} [built]
[7] ./~/font-awesome/fonts/fontawesome-webfont.eot?v=4.7.0 82 bytes {0} [built]
[8] ./~/font-awesome/fonts/fontawesome-webfont.svg?v=4.7.0 82 bytes {0} [built]
[9] ./~/font-awesome/fonts/fontawesome-webfont.ttf?v=4.7.0 82 bytes {0} [built]
[10] ./~/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0 84 bytes {0} [built]
[11] ./~/font-awesome/fonts/fontawesome-webfont.woff?v=4.7.0 83 bytes {0} [built]
[12] ./~/ieee754/index.js 2.05 kB {0} [built]
[13] ./~/isarray/index.js 132 bytes {0} [built]
[14] (webpack)/buildin/global.js 509 bytes {0} [built]
Webpack Bundle Analyzer saved report to C:\NEW_StudentLock_Core\AspNetCoreSpa\wwwroot\dist\report.html
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Users\\Azayzel\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "build:prod"
npm ERR! node v6.6.0
npm ERR! npm v3.10.7
npm ERR! code ELIFECYCLE
npm ERR! aspnetnetcore@0.0.0 build:prod: `node node_modules/webpack/bin/webpack.js --config config/webpack.prod.js --env.prod`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the aspnetnetcore@0.0.0 build:prod script 'node node_modules/webpack/bin/webpack.js --config config/webpack.prod.js --env.prod'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the aspnetnetcore package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node node_modules/webpack/bin/webpack.js --config config/webpack.prod.js --env.prod
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs aspnetnetcore
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls aspnetnetcore
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\NEW_StudentLock_Core\AspNetCoreSpa\npm-debug.log
C:\NEW_StudentLock_Core\AspNetCoreSpa\StudentLock.csproj(23,5): error MSB3073: The command "npm run build:prod" exited with code 1.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
dotnet publish Error: The process cannot access the file ...
I get the following error when tring to run dotnet publish : The process cannot access the file because it is being used...
Read more >Publish error - the process cannot access the file
This error is caused by concurrency when two or more different processes try to access and lock the same file. A quick action...
Read more >Files will not publish - Canvas Community
My issue was that the file that I was unable to fully publish was in a hidden folder. So, I navigated to the...
Read more >After updating VS To 17.6.4, not publishing to configured ...
I just updated to version 17.6.4 from 17.3.x and since the update, I am unable to successfully run any of my ClickOnce publish...
Read more >Publish doesn't work in Visual Studio 16.3.1
If so, please delete and re-create this pubxml. ... Right click the project name and choose 'Open Folder in File Explorer', delete all...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok, when adding
-f
to npm build in .csproj, it builds perfect.Tried the above and i still get the below…