4 ms·
I’m scrolling and scrolling waiting for a paragraph that tries to sell me on why I’d bother and risk upgrading. I think the best I got were patch notes. Any go
by Waterluvian 6y ago
I’m scrolling and scrolling waiting for a paragraph that tries to sell me on why I’d bother and risk upgrading. I think the best I got were patch notes.
Any good reason to upgrade?
- acemarke 6y agoPer https://webpack.js.org/blog/2020-10-10-webpack-5-release/#general-direction https://webpack.js.org/blog/2020-10-10-webpack-5-release/#ge... : - Improve build performance with Persistent Caching. - Improve Long Term Caching with better algorithms and defaults. - Improve bundle size with better Tree Shaking and Code Generation. - Improve compatibility with the web platform. - Clean up internal structures that were left in a weird state while implementing features in v4 without introducing any breaking changes. - Prepare for future features by introducing breaking changes now, allowing us to stay on v5 for as long as possible
- randtrain34 6y agoAre there any benchmarks to get a rough idea on how much improvement in all these areas we can expect to get by upgrading?
- xwdv 6y agoThe only benchmark that matters is how much more money you will make from customers after upgrading.
- dmitryminkovsky 6y agoPut that coffee down! Coffee is for closers only.
- lhnz 6y agoI've heard that build performance is actually worse than webpack 4, if you're not using persistent caching. See: https://twitter.com/FredKSchott/status/1314220659984146432 https://twitter.com/FredKSchott/status/1314220659984146432
- nicoburns 6y agoFrom that thread: The benchmark is dominated by terser and SourceMap performance. What you see are different terser configurations. Webpack 4 with compress.passes: 1 and webpack 5 with compress.passes: 2. Enabled SourceMaps makes minimizing extra expensive.
- foota 6y agoI'm excited for async module loading for web assembly.
- jholman 6y agoMacOS's broken-ass filesystem will no longer be allowed to cause warnings on other operating systems, that's a feature I'm keen about! (removal of the dependency on chokidar and fsevents)
- Waterluvian 6y agoHaha oh man. That one always gets me messages from the newcomers.
- deleted 6y ago[deleted]
- bichiliad 6y agoThe biggest thing I've been excited about is having an offline cache for fast recompilations. It'll make startup times a lot faster, which is a big improvement for developer experence (especially in larger codebases).
- marcins 6y agoUp to a point, eventually when the code base is large enough you spend more time serialising/deserialising and passing things between workers that it can be faster to disable the cache.
- bichiliad 6y agoAre you saying that from experience with webpack 5, or is that a prediction?
- marcins 6y agoFrom experience with one of the later betas (around 22 or 23?) we saw no improvement or slight regression with the disk cache vs the memory cache for incremental builds. Initial builds (warm starts) were faster, but there was still significant overhead reading the cache - this is an area where any optimisation would yield big results. I haven't had the chance to try the released version yet, but my understanding is there weren't any significant changes in this area.
- spankalee 6y agoSupport for import.meta.url is huge, especially inside fetch() and new URL().
- rikroots 6y agoThank you for making this comment - without it I would've ignored this new release. Failure of bundlers (Webpack, Parcel, Rollup, etc) to support import.meta.url has been a major headache for me. Making my JS library usable in sites that use such bundlers in their build chain has led to me making some - questionable, let's say - decisions in the library's code. The sooner I can remove my "solutions", the happier I will be!
- NoInkling 6y agoThe parser was updated which brings the ability to use new (stage 4) ES syntax without having to transpile: - Nullish coalescing - Optional chaining - Numeric separators - Logical assignment operators I'm surprised it wasn't mentioned in the notes -- I guess everyone is transpiling for production anyway, but it's still nice not having to do so in development. Now if only they had a way to activate support for stage 3 features (https://github.com/acornjs/acorn-stage3 https://github.com/acornjs/acorn-stage3) so all the class field stuff could be added to that list (modern browsers have already supported it to varying degrees for a while now).