Skip to content

Migrate to Webpack 5 - #218

Merged
abhishek-kaushik merged 7 commits into
mainfrom
upgrade-webpack-5
Sep 9, 2025
Merged

Migrate to Webpack 5#218
abhishek-kaushik merged 7 commits into
mainfrom
upgrade-webpack-5

Conversation

@abhishek-kaushik

@abhishek-kaushik abhishek-kaushik commented Sep 4, 2025

Copy link
Copy Markdown
Member

Major Changes

1. Webpack 5 Migration

  • Updated webpack from v4 to v5.101.3
  • Updated webpack-cli to v6.0.1
  • Updated webpack-dev-server to v5.2.2
  • Modified webpack configuration to be compatible with Webpack 5

2. ESLint Migration to v9 with Flat Config

  • Replaced deprecated @humanmade/eslint-config
  • Created modern eslint.config.mjs using ESLint 9's flat config format
  • Removed .eslintignore and .eslintrc.js (replaced by flat config)
  • Updated to ESLint 9.34.0

3. Dependencies Overhaul

  • Updated numerous webpack-related packages for v5 compatibility
  • Updated build tooling and loaders
  • Cleaned up peer dependencies

4. Configuration Updates

  • Updated loader configurations for Webpack 5 compatibility
  • Modified plugin configurations
  • Updated test configurations

Breaking Changes

  • Webpack 5: This is a major version upgrade with breaking changes
  • ESLint 9: Requires flat config format, older ESLint configs won't work
  • Node.js: Likely requires newer Node.js versions for Webpack 5 support

@abhishek-kaushik
abhishek-kaushik marked this pull request as ready for review September 4, 2025 18:30
Comment thread docs/guides/getting-started.md
@mattheu

mattheu commented Sep 4, 2025

Copy link
Copy Markdown
Member

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!

@mattheu

mattheu commented Sep 4, 2025

Copy link
Copy Markdown
Member

@mattheu

mattheu commented Sep 4, 2025

Copy link
Copy Markdown
Member

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

@abhishek-kaushik

Copy link
Copy Markdown
Member Author

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!

Yeah, there was a PR from Ignacio as well, I thought I am gonna start freash

@abhishek-kaushik

Copy link
Copy Markdown
Member Author

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, that's why I did not think much for backward compatibility

@kadamwhite

Copy link
Copy Markdown
Contributor

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!

@abhishek-kaushik abhishek-kaushik self-assigned this Sep 9, 2025

@joehoyle joehoyle left a comment

Copy link
Copy Markdown
Member

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

@abhishek-kaushik

Copy link
Copy Markdown
Member Author

@joehoyle , Added nvmrc file and updated Read me as well

@abhishek-kaushik
abhishek-kaushik merged commit b0d6fab into main Sep 9, 2025
1 check passed
@abhishek-kaushik
abhishek-kaushik deleted the upgrade-webpack-5 branch September 9, 2025 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants