-
Notifications
You must be signed in to change notification settings - Fork 307
Enhancement: Allow for multiple entries in our webpack config #238
Comments
Hello, thanks for opening an issue. This is most likely failing because we mainly use webpack for watching and bundling and not all of the other features it provides. We are contemplating how much of webpack to use in our app-scripts, but in the meantime if you are looking to implement a fully custom webpack build you may be better off building it from scratch instead of trying to implement it on top of app-scripts. I am going to leave this issue open as the team discusses how much of webpack we want to use. |
I'm in the process, however i would loss the |
Well |
Hi, I'm actually building the scss files as separate files at the moment (wp/ios/md), this is something I do using the entry points. I could see if I could get it to work by require-ing instead but this is also breaking my existing app as well. |
We may do this with the multiple entry points down the line but I doubt it will happen in the short term. I wouldn't plan on it as it's not presently on our roadmap. Thanks, |
Understandable, I still have issues getting anything working with webpack and these scripts. If I find out how or anyone has an idea, let me know! |
Dear @danbucholtz , why multiple entries is important ?
i have finished a mobile server which can do direct update like MobileFirst server, if ionic team think to include direct update technic and mobile server services , it will be my pleasure to work with ionic team. |
Sorry, this is outside of the scope of what we intend to support. Perhaps in the future. Thanks, |
@danbucholtz I think it should be. We should reduce the time when we are developing(web worker is nice but not enough) and the way to do this is not generating the bundle with vendors every time we change our code. We only want to change our code not all the bundle. To do this in my other @angular web projects I used systemjs and systemjs-builder you can check it out. @luchillo17 @jgw96 @msegers @BahgatMashaly @mlynch Regards, |
Not only that but tweaking the config to use DLL's would speed a WHOLE lot the compilation duration, such thing works best if we could configure better the entries for webpack. |
Short description of the problem:
In webpack 1 & 2 you could just specify multiple entry points to be processed like this:
However the output with
ionic-app-scripts@beta
is the following:What behavior are you expecting?
I expect webpack to let me specify multiple entry points and produce multiple output files.
Steps to reproduce:
ionic start buildTest sidemenu --v2 --ts
with[email protected]
cli installed.@ionic/[email protected]
for webpack support.mkdir config && cp node_modules/@ionic/app-scripts/config/webpack.config.js config/
.config/webpack.config.js
entry property to the presumably equivalent one like this:Which @ionic/app-scripts version are you using?
Using
@ionic/[email protected]
with custom webpack config.The text was updated successfully, but these errors were encountered: