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 #522

Merged
merged 1 commit into from Aug 29, 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 29, 2020

Codecov Report

Merging #522 into master will increase coverage by 0.01%.
The diff coverage is 87.50%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #522      +/-   ##
==========================================
+ Coverage   97.52%   97.53%   +0.01%     
==========================================
  Files           8        8              
  Lines         202      203       +1     
  Branches       55       56       +1     
==========================================
+ Hits          197      198       +1     
  Misses          5        5              
Impacted Files Coverage Δ
src/postProcessPattern.js 90.90% <83.33%> (-0.21%) ⬇️
src/index.js 100.00% <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 13cebc1...5b34dbf. Read the comment docs.

@alexander-akait alexander-akait merged commit 714af2f into master Aug 29, 2020
@alexander-akait alexander-akait deleted the fix-compatibility-with-webpack-5 branch August 29, 2020 16:00
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