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.

Sign up for GitHub

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

Jump to bottom

The package is empty on npm #107

Closed
jquense opened this issue Jul 10, 2018 · 1 comment
Closed

The package is empty on npm #107

jquense opened this issue Jul 10, 2018 · 1 comment
Labels
bug 🐛 Oh no! A bug or unintented behaviour.

Comments

@jquense
Copy link

jquense commented Jul 10, 2018

Looks like the .3 was published with nothing in it to @latest
@ryan-roemer ryan-roemer added bug 🐛 Oh no! A bug or unintented behaviour. high priority labels Jul 10, 2018
@ryan-roemer ryan-roemer mentioned this issue Jul 10, 2018
Closed
3 tasks
@kitten
Copy link
Member

kitten commented Jul 10, 2018

sorry about that! Accidentally published 0.3.0-next3 to latest instead of next. Should be all fixed up now 👍

Thanks for the quick issue 🎉

@kitten kitten closed this as completed Jul 10, 2018
kitten added a commit that referenced this issue Feb 5, 2020
@kitten
Add traversal stack to all errors and warnings (#107)
cb044d2 
* Replace warning with imperative warn

We're almost always doing warning(false, ...)
so it's not worth keeping the first argument around.

* Add debug stack for help.ts

For collecting some nodes as they're traversed for helpful
debugging output.

* Add pushDebugNode to all relevant traversal points

* Update transform-invariant-warning

* Prevent debug stack from being included in minified build
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug 🐛 Oh no! A bug or unintented behaviour.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jquense @ryan-roemer @kitten