-
Notifications
You must be signed in to change notification settings - Fork 13
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
@rdfjs/types 1.1.1 exported to npm as empty package #49
@rdfjs/types 1.1.1 exported to npm as empty package #49
Comments
cc @matthieubosquet - I suspect this comes from #47 |
Good grief. Fixing ASAP |
I am not familiar with the @changeset/cli and I am surprised that it is inconsistent with Note that when I run I notice a lot of warnings on the release action run. I looked up changeset but none of the commands gave me anything explicit as to how the package is created. |
It should be consistent, of course, and I'm surprised we ran into that issue. Investigating now |
The warnings show we're using an old version of the changesets action. Could be the reason for failure |
I unpublished the |
I also tried a So, a manual publish from local should work if you can do that @tpluscode (and thank you for jumping on this so promptly). |
Apparently the issue is with yarn. When I run There are open issues on GitHub about |
That's an interesting find. |
@tpluscode I found a file pattern that works with both yarn and npm: I prefer using I personally use a very simple action that triggers on GitHub Release to publish my packages to npm. |
Changesets do not depend on |
That's great to know (and makes way more sense)! |
https://www.npmjs.com/package/@rdfjs/types/v/1.1.1?activeTab=code
The latest @rdfjs/types package has just been pushed to npm... without any types!
Understandably, this is causing some ecosystem issues... 😉
(@rdfjs @tpluscode et al.)
The text was updated successfully, but these errors were encountered: