-
Notifications
You must be signed in to change notification settings - Fork 3
Migrate to Webpack 5 #218
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
Migrate to Webpack 5 #218
Conversation
|
I know there was a branch with some effort done towards this but it's been a while now and I forget what ultimately blocked this. Either way awesome to pick this up and try get it done! |
|
FWIW I don't care so much about breaking changes. It's a new major version and we have to move forwards. As long as we have them documented |
Yeah, there was a PR from Ignacio as well, I thought I am gonna start freash |
Yeah, that's why I did not think much for backward compatibility |
|
I don't think anything particularly blocked #205 beyond nobody taking the time to follow through on it. Thanks for this, I'm fine starting fresh! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@abhishek-kaushik could we document or add a constraint for the nodejs supported version? Not sure if that can be in package.json or the readme
|
@joehoyle , Added |
Major Changes
1. Webpack 5 Migration
2. ESLint Migration to v9 with Flat Config
@humanmade/eslint-configeslint.config.mjsusing ESLint 9's flat config format.eslintignoreand.eslintrc.js(replaced by flat config)3. Dependencies Overhaul
4. Configuration Updates
Breaking Changes