-
Notifications
You must be signed in to change notification settings - Fork 18
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
[BUG]: dist-types/index.d.ts is not present in the published NPM package #405
Comments
I started checking this: Here are two logs comparing a release with types and without types: Release
|
Ok, so... the root cause of this issue is the following one, I think: Apparently, since The generated "files": [
"dist-*/",
"bin/"
], The fix would be as easy as adding "files": [
"dist-*/**",
"bin/**"
], Since these lines are auto-generated and I guess the quick solution is to use What do you think @octokit/extensibility-sdks @octokit/js-community? |
@oscard0m thank you for the investigation here! That's fascinating. I know npm 9 was released in October; I wonder why this is just happening now. Perhaps it's related to a shift in the LTS version in our node setup? Pinning down a date would help with the solution I think: if we started using npm 9 to release immediately before the issue was reported, a rollback seems appropriate. If we've been using npm 9 since October, rolling back a major version may have additional complications to think about. |
We used to explicitly define a requirement on Would we be able to patch the files afterwards pika has built the package before |
… in "files" You can read more here: #405
@kfcampbell opened a PR with @wolfy1339 's proposal as a hot fix (with some question marks) and opened a discussion to talk about a strategy for a long-term solution: octokit/octokit.js#2403 |
… in "files" You can read more here: #405
… in "files" You can read more here: #405
Thanks for showing me to this issue @wolfy1339. I patiently await updates. |
* fix(ci): add hotfix in built package.json to use proper file patterns in "files" You can read more here: #405 * ci(release): run 'scripts/fix-package-json.js' before release
🎉 This issue has been resolved in version 4.1.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Here's a comparison of exported files from 4.1.2 and 4.1.3: Published files in
|
Omg, if this is actually done I will buy everyone involved a beer. |
@maxnachlinger @Ddupasquier did you have a chance to try this? Did your problems get solved? |
@oscard0m forgive me for not circling back. Your dazzling fix solved the issue! :) |
No problem! I was just going through my old notifications and I just wanted to double-check everything was working again. I'm happy we unblocked you @maxnachlinger :) |
@oscard0m In order to give you an accurate answer I will have to revisit the component and remember what I was even doing haha. On first view of the code... No. But this could be a syntax issue on my part or maybe my token expired. |
@oscard0m AH! So if you check the 'unrelated comments' a little ways up between @wolfy1339 and I, it seems that the issue from the octokit side is solved. But success in my project is still blocked haha. |
Yep, the |
Absolutely. I appreciate everyone's dillogence! |
What happened?
Hey awesome maintainers! After upgrading from 4.1.1 to 4.1.2 I noticed the following tsc error:
Having a look in the tgz on npm I only see a
dist-node
directory, but the package.json exports the types indist-types/index.d.ts
Versions
"@octokit/core": "4.2.0"
"@octokit/plugin-retry": "4.1.2",
"@octokit/rest": "19.0.7",
node 16.19.1
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: