-
-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npx webpack
fails immediately after au new
#1134
Comments
Unfortunately our default setup uses gulp task to wrap around webpack config. There is a PR going on to simplify our webpack setup, hopefully removing gulp wrapper from the setup. #1105 |
Aurelia 2 default skeleton will let webpack be just webpack. |
We are working on it in https://github.com/aurelia/new, I will get some very basic up in few days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a bug report
Local aurelia-cli v1.0.2
"aurelia-bootstrapper": "^2.3.2",
"aurelia-animator-css": "^1.0.4"
"aurelia-cli": "^1.0.2",
"aurelia-testing": "^1.0.0",
"aurelia-tools": "^2.0.0",
"aurelia-webpack-plugin": "^3.0.0",
Please tell us about your environment:
Operating System:
Windows Server 2012 R2 (up to date)
Node Version:
12.6.0
NPM Version:
6.9.0
Browser:
Chrome
Language:
TypeScript
Loader/bundler:
Webpack
I have done an embarrassing amount of testing and research in order to land at the conclusion that I should probably create an issue for this.
I've reproduced this problem on two different computers.
Steps:
npm install -g aurelia-cli
cd (mkdir c:\code\test\au-wp)
(Powershell)au new aurelia-app -u -s http2,dotnet-core,typescript,htmlmin-min,sass,vscode,scaffold-navigation
cd aurelia-app
npm install
npx webpack .\webpack.config.js
Note that
au build
does work properly, and I believe that has something to do with how the aureliabuild.ts
task does a bunch of magic before manually invoking webpack.If this is by design, I feel like it should be documented somewhere.
Current behavior:
Errors when building with webpack
Click to view the output and errors
What is the expected behavior?
npx webpack .\webpack.config.js
should succeed without errors.What is the motivation / use case for changing the behavior?
If there's a
webpack.config.js
file, it seems like I should be able to build withnpx webpack .\webpack.config.js
. If this is by design, I feel like it should be documented somewhere.The text was updated successfully, but these errors were encountered: