-
Notifications
You must be signed in to change notification settings - Fork 3
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
Release 2.0.0 to npm #16
Comments
Okay, something must have thrown off semantic-release, I'll see if I can sort this out and upgrade ast-types as well. |
Actually I'm confused what you mean, I see 2.0.0 on npm via the website and |
Maybe I confused it with |
I think what you meant is that Btw sometimes with yarn at least to ensure I get the latest version of a transitive dep, I have to remove the primary deps and then add them back, |
argh hang on, I accidentally published |
Actually I think |
Do you know if |
In 0.x any minor bump is considered breaking so package managers won't pull in 0.11 if you declare While I don't think you should ever use |
I guess I should use |
forgot to close this |
2.0.0 was released on GitHub but npm doesn't include it.
/cc @jedwards1211
When
jscodeshift-find-imports
is released on npm can we at the same time updatejscodeshift-add-imports
.Right now
jscodeshift-add-imports
pulls in an older version ofast-types
that I'd like to get rid of.The text was updated successfully, but these errors were encountered: