-
Notifications
You must be signed in to change notification settings - Fork 310
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]: No "exports" main defined
in version 6.0.1
#665
[BUG]: No "exports" main defined
in version 6.0.1
#665
Comments
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labled with |
We switched to ESM and you need to use the following options in your
|
Hi, thank you, unfortunately after adding that, the issue still persists. :( |
You need to use ESM, right now your are outputting CJS |
* fix(pkg): add a default fallback See #665 #667 * fix(pkg): add an export for `dist-types/types.d.ts` Many people are importing from `dist-types/types.d.ts`, and the switch to ESM prevents them from using any of the types defined in that file. * fix: mark `graphql` import as a type import * docs: add note on needed config changes for TypeScript
🎉 This issue has been resolved in version 6.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
* fix(pkg): add a `default` fallback export See octokit/core.js#665 octokit/core.js#667 * docs(README): add note on needed config changes for TypeScript
* fix(pkg): add a default fallback See octokit/core.js#665 octokit/core.js#667 * docs: add note on needed config changes for TypeScript
What happened?
I updated @octokit/core to v6.0.1 and now I get the following error. See skaut/poptavky#1373
Versions
@octokit/core
v6.0.1Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: