Skip to content
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

fix: make webpack optional peer dependency #4778

Merged
merged 1 commit into from Mar 18, 2023

Conversation

hardfist
Copy link
Contributor

@hardfist hardfist commented Mar 17, 2023

  • This is a bugfix
  • This is a feature
  • This is a code refactor
  • This is a test update
  • This is a docs update
  • This is a metadata update

For Bugs and Features; did you add new tests?

No, not easy to test in this repo

Motivation / Use-Case

fixes #4776

Breaking Changes

No

Additional Info

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Mar 17, 2023

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: hardfist / name: hardfist (bea6143)

Comment on lines +142 to 145
},
"webpack": {
"optional": true
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You may also want to remove it from the peerDependenciesfield above

"webpack": "^4.37.0 || ^5.0.0"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we remove webpack from peerDependencies it would mean any webpack version would be ok for webpack-dev-server but webpack-dev-server did require specific webpack version according to the documentation of https://pnpm.io/next/package_json#peerdependenciesmetaoptional

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, we still need versions, in theory this PR can break a code for some inattentive developers (which ignored warnings from package managers), if you don't have webpack in dependcies and rely on the new behaviour of npm (autoinstall peer deps), but it should be fixed on their side, because you should always list of you dependecies

@codecov
Copy link

codecov bot commented Mar 18, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (4e84607) 92.05% compared to head (bea6143) 92.05%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #4778   +/-   ##
=======================================
  Coverage   92.05%   92.05%           
=======================================
  Files          16       16           
  Lines        1662     1662           
  Branches      622      622           
=======================================
  Hits         1530     1530           
  Misses        121      121           
  Partials       11       11           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

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.

Add webpack as optional peer dependency
3 participants