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

chore: improve webpack 5 initial test #6493

Merged
merged 1 commit into from
Apr 27, 2021
Merged

Conversation

sorrycc
Copy link
Member

@sorrycc sorrycc commented Apr 27, 2021

Checklist
  • npm test passes
  • tests are included
  • documentation is changed or added
  • commit message follows commit guidelines
Description of change

@codecov
Copy link

codecov bot commented Apr 27, 2021

Codecov Report

Merging #6493 (1c6b064) into master (0867356) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #6493      +/-   ##
==========================================
- Coverage   84.76%   84.71%   -0.05%     
==========================================
  Files         157      157              
  Lines        3583     3585       +2     
  Branches      986      989       +3     
==========================================
  Hits         3037     3037              
- Misses        536      538       +2     
  Partials       10       10              
Impacted Files Coverage Δ
packages/umi/src/initWebpack.ts 0.00% <0.00%> (ø)

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 0867356...1c6b064. Read the comment docs.

@sorrycc sorrycc merged commit 05de48d into master Apr 27, 2021
@delete-merged-branch delete-merged-branch bot deleted the fix/webpack-5-init-problem branch April 27, 2021 09:03
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.

None yet

1 participant