Angular-cli: investigate parcel

[tycho01]

Recently it seems a new bundler has popped up named parcel (github, site). I haven't looked into it in detail, but it appears to be claiming some advantages over webpack. If that's the case, it might be of interest here as well.

[hansl]

Hello @tycho01,

Thanks for the report. We're not looking at changing our build system from webpack right now. We keep an eye on new bundlers and if there's a point where it would make sense we'll consider it.

I'm going to close this as it is not something I can see us considering for the foreseeable future.

[alexandermikuta]

If with webpack 4 things do not get better I hope you reconsider your decision not to investigate in parcel.
Currently our build-times in a larger project are several minutes and sometimes we get out-of-memory issues. Also we are quite happy with angular-cli in all other aspects we currently consider switching away from cli because of this build-issues.

[dankellett]

92%

[webmutation]

Ditto... webpack is slow. Our app takes 6 mins to build !!!

[zuohuadong]

Ditto...

[tatsujb]

common, two years going on three and still no official support/definitive replacement of webpack with parcel?

or rollup, or @pika/web (https://github.com/pikapkg/web) , who cares, anything to free us from this.

@dankellett what was this 92% about?

[leak]

@tatsujb Presumably this is a reference to the percentage that webpack is stuck at for quite a while before actually finishing.

[tatsujb]

@leak nah I don't think so. webpack usually sticks at 11% or 69% you barely ever get to see the final percentages.

EDIT : can this PLEASE be opened as a new issue or reopened :

Here's a quick and incomplete breakdown of the issues plaguing webpack :

• On a frequent basis webpack gets out of sync with the current state of the project and will fall behind 1 or N (yes it really can be unlimited in how far back) builds. You're then coding while working with a "phantom build" or "ghost build" a served state of the app which is 1 or N compiles behind what you currently have on disk / in your IDE. this is impossible to flag/debug. You must be aware this can happen and remember to think about it constantly when something iffy is happening (old state of the code clearly on page / not expected behavior) and react by killing all npm instances on your PC and compiling from scratch.
  Worst part about this is that it can sometimes be chimeric : a little of the current state a little of an old state. which leads to truly aberrant behavior.
  You can waste a lot of time debugging your code over this when in reality your code was 100% correct.
• Speaking of time, webpack is very slow. If you use rollup, parcel or another solution on your angular cli project, initial compilation will be super-fast by comparison and the following re-compilations even more so.
• Webpack has loads of complicated config. Parcel for one has NO config. with that being a possibility why are we trudging on with a dated config-heavy solution?

[SubJunk]

Yeah building in prod mode stays at 92% for ages. Would love to see the speeds improve with something like Parcel!

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{_This action has been performed automatically by a bot._}