-
Notifications
You must be signed in to change notification settings - Fork 132
feat!: move to esm-only #246
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
Conversation
🦋 Changeset detectedLatest commit: ccc9b17 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Open in Stackblitz • @example/basic • @example/changesets
commit: |
@@ -18,4 +18,5 @@ jobs: | |||
node-version: 20 | |||
cache: "pnpm" | |||
- run: pnpm install | |||
- run: pnpm build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing this worked before because we used bundler
resolution which basically tells typescript not to care so much about unresolved imports
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Just going to hold off on merging until #250 lands.
Migrates to emitting only ES modules now that `require(esm)` is supported in all LTS versions of node other than the soon-to-die-off 18.x.
Otherwise the `core` package won't have a `dist/` output to resolve DTS files during `tsc`.
3bbd99a
to
41f359a
Compare
Migrates to emitting only ES modules now that
require(esm)
is supported in all LTS versions of node other than the soon-to-die-off 18.x.