Skip to content

feat!: publish only esm output#36

Merged
chenjiahan merged 1 commit into
mainfrom
chenjiahan/chore-esm-only-output
Apr 13, 2026
Merged

feat!: publish only esm output#36
chenjiahan merged 1 commit into
mainfrom
chenjiahan/chore-esm-only-output

Conversation

@chenjiahan
Copy link
Copy Markdown
Member

Summary

  • Only build and publish the ESM bundle plus declaration files.
  • Remove CJS-specific package entry fields so the published metadata matches the generated output.
  • Validate the change with pnpm lint and pnpm build.

Related Links

  • None

@chenjiahan chenjiahan marked this pull request as ready for review April 13, 2026 03:00
Copilot AI review requested due to automatic review settings April 13, 2026 03:00
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the library build and package metadata to publish ESM-only output (plus .d.ts) and remove CommonJS-oriented entrypoints so package.json matches the generated artifacts.

Changes:

  • Configure rslib to emit only an ESM build with TypeScript declarations.
  • Update package.json exports to a single ESM entry and simplify the published files list.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
rslib.config.ts Removes the CJS build target; keeps ESM + dts generation.
package.json Adjusts exports and removes legacy entry fields to align with ESM-only publishing.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread package.json
Comment thread package.json
@chenjiahan chenjiahan changed the title chore: publish only esm output feat!: publish only esm output Apr 13, 2026
@chenjiahan chenjiahan merged commit 9787a11 into main Apr 13, 2026
9 checks passed
@chenjiahan chenjiahan deleted the chenjiahan/chore-esm-only-output branch April 13, 2026 03:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants