-
Notifications
You must be signed in to change notification settings - Fork 67
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
Bump magic-string #184
Bump magic-string #184
Conversation
Oh no! CI is failing, but only for Node 4 and 6. These are the failing tests:
@Rich-Harris Any insights here as to why magic-string version upgrade would induce these failing tests? |
That's actually a change in acorn. |
Aha! Excellent insight! Thank you @adrianheine . |
I just pushed 77ab236 to fix that. |
Closing in favor of #185 |
I think this one could be merged much quicker than #185, see my comments there. |
@adrianheine Makes sense. I merged latest master, should be good to go. |
Most of your changes to |
Yes, I was a bit confused about those changes myself. I apologize if they cause problems. These are the Node and NPM versions I'm on:
Perhaps best to use your generated version of package-lock, with fewer changes? |
Yeah, keeping my version would be nice since I'm currently the person doing most of the commits in this project. Ideally a |
Closing in favor of #186 , as the commits here would make a mess in Git history. |
btw, I'm absolutely willing to invest some work squashing otherwise good commits, and you could have used |
Ah, good to know for future work. Thanks for the tips! |
Closes #183