-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Webpack 5 support #8102
Comments
Regarding:
I'm using a forked version because as you noted, it hasn't been updated for a while. This only depends on the latest version of |
@Blfrg thanks, updated into the initial post :) |
@IlCallo just a little update: workbox-webpack-plugin v6(stable) is released, and the latest version is v6.0.2. |
Perfect, updated into the first post |
@IlCallo There is a temporary fork of postcss-rtl that's been upgraded to work with latest postcss plugin structure. |
I added this to the original post, but I'm not sure taking the burden of yet another package to maintain for ourselves is the right way... |
I agree. I am using |
FYI the vue fork of |
Thanks! One or two out of the list then :D |
Regarding:
I was just reviewing my dependencies and noticed that back in December @sodatea merged the needed PR So the original dependency can be considered reliable again, instead of the fork. |
Thanks, updated in the initial list |
html-webpack-plugin v5 has been upgraded to the latest stable version long ago . |
Just as a note, as |
We need to first concern about our current user base and not leave them hanging with their current apps. Due to Webpack team not upgrading We are aware of how good Vite is, which is why we've planned a Vite plugin and even a Quasar CLI based on Vite instead of Webpack. It will come, guaranteed. I'm about to finalize the Webpack 5 upgrade (a few more days and there's going to be a q/app release with it) and then it's Vite time! |
Mulțumesc, Razvan :) |
"@quasar/app" v3.0.0-beta.16 will feature Webpack 5. Was hell upgrading everything (including our many of custom webpack plugins). But while I was at it, took time to also greatly improve and revamp the inner workings of q/app (and there are so many to list them here!). Get ready to rock'n'roll your apps with it! |
Available through "@quasar/app" v3.0.0-beta.16 + Quasar v2.0.0-beta.13. Enjoy and please read the release notes! https://github.com/quasarframework/quasar/releases/tag/%40quasar%2Fapp-v3.0.0-beta.16 |
https://webpack.js.org/blog/2020-10-10-webpack-5-release/
https://webpack.js.org/migrate/5/
webpack 5 is out and it's time we go way down into that rabbit hole :D
We'll use this issue to keep track of everything.
We plan to ship Quasar 2 with Webpack 5 support, or add it right after with a
@quasar/app
update,but could push back the upgrade to Quasar 3 if we find out there are too many breaking changes for devsthis is needed as some webpack 4 issues are pretty severeIf anyone from team or community wants to jump in and point out something we are missing, both on current issues or new features we can leverage, please do :)
Let's avoid spam and "+1", we are going to delete/hide those comments
Existing issues due to webpack 4
New feature we want to leverage from webpack 5
??
andexport * as ...
. This should allow us to avoid using babel in some cases@types/webpack-*
packages and reduce conflicting types problemsimport {date} from 'quasar; const { ... } = date
syntaxLoaders to upgrade
we are on v4 right now, we need to upgrate to v6, webbpack 5 is there since v5upgraded to v6not updated since years, webpack 5 status support unknown. Consider using this updated fork insteadUpdated in december to support Pug 3 and webpack 5supports webpack 5 apparently since v8.0.1, we ship with v7.0.5.We already ship with v8, we may consider upgrade to v9 (drops webpack v4 support and require node v12).(currently in RC phase). We should ditch v5 support and update everything to use v6 only.writeToDisk
option. This dependency should be removedIssues with webpack 5 migration
webpack-dev-server v4 (with chokidar v3) [has been released as 4-beta.0] but there are still a number of bugs and breaking changes not applied, better wait some more time before migrating it (V4 webpack/webpack-dev-server#2592) webpack-dev-server 3.11.0 is not fully compatible to webpack 5 webpack/webpack-dev-server#2807These PRs/issues has been solvedwebpack-dev-server v4 uses webpack-dev-middleware v4, which contains many breaking changesStable version has been releasedhtml-webpack-plugin v5All upstream bugs has been fixed and v5 has been released as stableis currently blocked due to upstream bugs webpack 5 <-> html-webpack-plugin 5 jantimon/html-webpack-plugin#1527is currently in beta and will soon be releasedworkbox-webpack-plugin v6 (lives in app-space, but we still need to add support for it in q/app) supports webpack 5has not been released as stable, but it's pretty close to beis now stable. Down side: we must fix workbox v6 breaking changes toovue-style-loader is many commits behind style-loader, which supports webpack 5. There is also a compatiblity issue with css-loader v4+. Critical css collection has not been tackled for Vue 3 release, and probably will in 3.1, so we're gonna switch to style-loader for nowpostcss-safe-parser
due to missing API oncss-minimizer-webpack-plugin
Related issues
Things which could be explored, but which aren't really "in-scope" for the migration
preload
support is still blocked, as both the upstreampreload-webpack-plugin
and the forked@vue/preload-webpack-plugin
are pretty much dead. We could ask the Vue team if they plan to update their fork, as I don't think the original repo will ever come backAdditional context
Vue CLI still has not switched, but something is moving:
React is moving there too and have an exaustive list of stuff to upgrade and problems to solve:
Angular CLI already supports Webpack 5 as experimental (we could check if we can learn something from their code), and is discussing about Module Federation feature:
The text was updated successfully, but these errors were encountered: