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: able to use a custom resolver #26

Merged
merged 1 commit into from
Jul 24, 2017
Merged

feat: able to use a custom resolver #26

merged 1 commit into from
Jul 24, 2017

Conversation

mastilver
Copy link
Owner

closes #13

@codecov-io
Copy link

codecov-io commented Jul 24, 2017

Codecov Report

Merging #26 into master will increase coverage by 0.07%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #26      +/-   ##
==========================================
+ Coverage   98.75%   98.82%   +0.07%     
==========================================
  Files           1        2       +1     
  Lines          80       85       +5     
==========================================
+ Hits           79       84       +5     
  Misses          1        1
Impacted Files Coverage Δ
src/index.js 98.76% <100%> (+0.01%) ⬆️
src/get-resolver.js 100% <100%> (ø)

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 4d63ed2...a6587c1. Read the comment docs.

@mastilver mastilver merged commit a5b5cb4 into master Jul 24, 2017
@mastilver mastilver deleted the custom-resolver branch July 24, 2017 23:10
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.

feat: add "resolver" options to be able to use a different cdn
2 participants