Skip to content

chore: include LICENSE in the published npm package - #35

Open
rawadtraboulsi wants to merge 1 commit into
better-auth:mainfrom
rawadtraboulsi:chore/include-license-in-npm-package
Open

chore: include LICENSE in the published npm package#35
rawadtraboulsi wants to merge 1 commit into
better-auth:mainfrom
rawadtraboulsi:chore/include-license-in-npm-package

Conversation

@rawadtraboulsi

Copy link
Copy Markdown

Summary

LICENSE is on main (#34) but the published @better-auth/utils@0.5.0 tarball does not include it. package.json lists "files": ["dist"], so the packed package is only dist, package.json, and README.md.

This adds LICENSE to files so the next publish ships the MIT license file with the package.

A patch release after this would put the file on npm.

Test plan

  • npm pack --dry-run lists LICENSE

Made with Cursor

LICENSE is already on main, but npm 0.5.0 only ships dist because files is ["dist"].
@greptile-apps

greptile-apps Bot commented Aug 15, 2026

Copy link
Copy Markdown

Greptile Summary

This PR updates the npm package allowlist so the existing MIT license is explicitly included in future published tarballs.

  • Adds LICENSE alongside dist in the package.json files array.

Confidence Score: 5/5

The PR appears safe to merge.

The manifest-only change explicitly includes the existing LICENSE file in npm package contents without altering runtime code, dependencies, exports, or build behavior.

Reviews (1): Last reviewed commit: "chore: include LICENSE in the published ..." | Re-trigger Greptile

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.

1 participant