Skip to content

chore: update webpack to 5.17.0 #2376

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

Merged
merged 3 commits into from
Jan 26, 2021
Merged

Conversation

snitin315
Copy link
Member

What kind of change does this PR introduce?
update webpack

Did you add tests for your changes?
yes
If relevant, did you update the documentation?
yes
Summary

Update webpack to 5.17.0
update options and commands.

Does this PR introduce a breaking change?
NO

Other information
Fixes #2373

@snitin315 snitin315 requested a review from a team as a code owner January 25, 2021 07:21
@codecov
Copy link

codecov bot commented Jan 25, 2021

Codecov Report

Merging #2376 (b651c90) into master (0d30eda) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2376   +/-   ##
=======================================
  Coverage   70.09%   70.09%           
=======================================
  Files          48       48           
  Lines        2117     2117           
  Branches      548      548           
=======================================
  Hits         1484     1484           
  Misses        633      633           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0d30eda...b651c90. Read the comment docs.

@alexander-akait alexander-akait merged commit c5a06f7 into master Jan 26, 2021
@alexander-akait alexander-akait deleted the chore/update-webpack branch January 26, 2021 11:39
@alexander-akait
Copy link
Member

Thanks

snitin315 added a commit to snitin315/webpack-cli that referenced this pull request Feb 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants