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: compatibility with webpack@5 #571

Merged
merged 1 commit into from
Aug 26, 2020

Conversation

alexander-akait
Copy link
Member

This PR contains a:

  • bugfix
  • new feature
  • code refactor
  • test update
  • typo fix
  • metadata update

Motivation / Use-Case

fix compatibility with webpack@5

Breaking Changes

No

Additional Info

No

@codecov
Copy link

codecov bot commented Aug 26, 2020

Codecov Report

Merging #571 into master will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #571   +/-   ##
=======================================
  Coverage   88.55%   88.55%           
=======================================
  Files           5        5           
  Lines         428      428           
  Branches       96       97    +1     
=======================================
  Hits          379      379           
  Misses         47       47           
  Partials        2        2           
Impacted Files Coverage Δ
src/index.js 87.85% <100.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 25b0ecd...09c1de5. Read the comment docs.

@alexander-akait alexander-akait merged commit 21832c7 into master Aug 26, 2020
@alexander-akait alexander-akait deleted the fix-compatibility-with-webpack@5 branch August 26, 2020 12:19
@ylemkimon ylemkimon mentioned this pull request Aug 31, 2020
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