github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 22:32:01 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #7967] [MERGED] fix(core): exclude tsconfig.json from published package #15904

New Issue
Closed
opened 2026-04-13 10:18:02 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 10:18:02 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/7967
Author: @GautamBytes
Created: 2/14/2026
Status: ✅ Merged
Merged: 2/16/2026
Merged by: @himself65

Base: canary ← Head: fix/exclude-tsconfig

📝 Commits (2)

  • 06d2009 fix(core): only publish the dist folder
  • a220ae6 fix(core): include src in files for dev-source resolution

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 packages/core/package.json (+4 -0)

📄 Description

Closes #7956

The @better-auth/core package currently publishes its internal tsconfig.json because it lacks a files whitelist in package.json. This causes editor type resolution errors for consumers, as the published tsconfig.json attempts to extend a tsconfig.base.json file that does not exist in the npm package tree.

This PR restricts the published files to the dist directory, ensuring internal configuration files are excluded from the registry.

Changes

  • Added "files": ["dist"] to packages/core/package.json.

This aligns @better-auth/core with the publishing strategy used in the main better-auth package.

Summary by cubic

Whitelist dist and src for @better-auth/core publishing to exclude internal config files like tsconfig.json and support dev-source resolution. Fixes editor TypeScript resolution errors caused by the previously published tsconfig.json extending a non-existent tsconfig.base.json (closes #7956).

Written for commit a220ae68a6. Summary will update on new commits.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/7967 **Author:** [@GautamBytes](https://github.com/GautamBytes) **Created:** 2/14/2026 **Status:** ✅ Merged **Merged:** 2/16/2026 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `fix/exclude-tsconfig` --- ### 📝 Commits (2) - [`06d2009`](https://github.com/better-auth/better-auth/commit/06d2009efc97b307ad7fc5836c1c8ca74e404400) fix(core): only publish the dist folder - [`a220ae6`](https://github.com/better-auth/better-auth/commit/a220ae68a6dffa7505f8f0b14620307f0107f2c7) fix(core): include src in files for dev-source resolution ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/core/package.json` (+4 -0) </details> ### 📄 Description Closes #7956 The `@better-auth/core` package currently publishes its internal tsconfig.json because it lacks a files whitelist in package.json. This causes editor type resolution errors for consumers, as the published tsconfig.json attempts to extend a tsconfig.base.json file that does not exist in the npm package tree. This PR restricts the published files to the dist directory, ensuring internal configuration files are excluded from the registry. Changes - Added "files": ["dist"] to packages/core/package.json. This aligns `@better-auth/core` with the publishing strategy used in the main better-auth package. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Whitelist dist and src for @better-auth/core publishing to exclude internal config files like tsconfig.json and support dev-source resolution. Fixes editor TypeScript resolution errors caused by the previously published tsconfig.json extending a non-existent tsconfig.base.json (closes #7956). <sup>Written for commit a220ae68a6dffa7505f8f0b14620307f0107f2c7. Summary will update on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 10:18:02 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#15904
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?