-
Notifications
You must be signed in to change notification settings - Fork 304
Custom webpack.config.js hangs build #290
Comments
I actually want my own webpack.config.js to be required. But it doesn't seem to work with these scripts. I Inject some SASS variables to have custom primary/accent colours and other config. I really need this to work to be able to upgrade. I'll look at source but for now it's breaking erryting! |
I have a custom webpack config that has an alias defined in the resolve section:
The problem is it fails to find the resolve before 'webpack started' message in the console. It errors out when transpiling. This only happens on a Windows machine and not on my Mac. Any ideas? Here is the output:
Thanks! |
Oh I did upgrade to the 0.0.41 release of build scripts. Still fails. |
The process described in the original report still hangs under 0.0.42. |
This should be fixed now. It hung because we had the same argument for Thanks, |
Confirmed fixed in 0.0.43 |
Short description of the problem:
Even without modifying, simply specifying a custom webpack configuration file causes both prod and dev builds to hang after apparent completion.
What behavior are you expecting?
Build process to indicate completion and return to shell.
Steps to reproduce:
ionic start --v2 scratch
cd scratch
cp node_modules/@ionic/app-scripts/config/webpack.config.js ./
scripts.build
inpackage.json
to read "ionic-app-scripts build --dev -w ./webpack.config.js" (--dev
is optional, same issue happens without it)npm i --save-dev @ionic/app-scripts/@0.0.39
(also optional, 0.0.38 has same problem)ionic build
(hangs afterbuild dev finished
)Which @ionic/app-scripts version are you using?
0.0.38, 0.0.39
Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
There are additional aliases and externals that I need to declare in the webpack configuration, so "please just use the stock config" isn't an option. Modifying the actual stock config underneath
node_modules/@ionic/app-scripts/config/webpack.config.js
isn't scalable, as it breaks both automated builds and builds from fresh repo clones.The text was updated successfully, but these errors were encountered: