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

Feat: nested webpack resolving in import option #295

Merged
merged 1 commit into from Oct 29, 2020

Conversation

cap-Bernardito
Copy link
Member

This PR contains a:

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

Motivation / Use-Case

Nested webpack resolving in import option

Breaking Changes

No

Additional Info

No

@codecov
Copy link

codecov bot commented Oct 29, 2020

Codecov Report

Merging #295 into master will decrease coverage by 0.18%.
The diff coverage is 88.88%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #295      +/-   ##
==========================================
- Coverage   96.13%   95.94%   -0.19%     
==========================================
  Files           3        3              
  Lines         336      345       +9     
  Branches      104      105       +1     
==========================================
+ Hits          323      331       +8     
- Misses         12       13       +1     
  Partials        1        1              
Impacted Files Coverage Δ
src/utils.js 96.29% <88.88%> (-0.26%) ⬇️

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 0584740...0f549af. Read the comment docs.

@alexander-akait alexander-akait merged commit 390aeba into master Oct 29, 2020
@alexander-akait alexander-akait deleted the feat-resolve-import-option branch October 29, 2020 13:42
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

2 participants