-
-
Notifications
You must be signed in to change notification settings - Fork 399
chore: migrate to npm #196
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #196 +/- ##
=======================================
Coverage 97.95% 97.95%
=======================================
Files 13 13
Lines 686 686
Branches 110 110
=======================================
Hits 672 672
Misses 13 13
Partials 1 1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I removed Node.js@6 from matrix (yes, we still support it, will be removed in the next major release) due npm is broken and can't install dependencies, babel is broken due broken Node.js feature mapping, jest randomly fails, because it works due old legacy lock file, after installation new lock file we got new version and new versions is fully broken with node@6 |
|
If someone wants to spend a lot of time on long debugging - PR welcome |
Summary
migrate to npm
ref: webpack/tsc#77
What kind of change does this PR introduce?
chore
Did you add tests for your changes?
No need
Does this PR introduce a breaking change?
No
If relevant, what needs to be documented once your changes are merged or what have you already documented?
Nothing