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

[PR #7262] [MERGED] chore: add --coverage.provider=istanbul to coverage script #7182

New Issue
Closed
opened 2026-03-13 13:27:01 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 13:27:01 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/7262
Author: @sukvvon
Created: 1/11/2026
Status: ✅ Merged
Merged: 1/11/2026
Merged by: @himself65

Base: canary ← Head: chore/vitest-coverage-scripts

📝 Commits (5)

  • c74dd7f chore(*/package.json): add '--coverage.provider=istanbul' to coverage scripts
  • e329423 chore(package.json): remove redundant coverage CLI options from root script
  • c08fe5a Merge branch 'canary' into chore/vitest-coverage-scripts
  • 49d0c53 Merge branch 'canary' into chore/vitest-coverage-scripts
  • 52e8979 Merge branch 'canary' into chore/vitest-coverage-scripts

📊 Changes

10 files changed (+10 additions, -10 deletions)

View changed files

📝 package.json (+1 -1)
📝 packages/better-auth/package.json (+1 -1)
📝 packages/cli/package.json (+1 -1)
📝 packages/core/package.json (+1 -1)
📝 packages/expo/package.json (+1 -1)
📝 packages/passkey/package.json (+1 -1)
📝 packages/scim/package.json (+1 -1)
📝 packages/sso/package.json (+1 -1)
📝 packages/stripe/package.json (+1 -1)
📝 test/package.json (+1 -1)

📄 Description

Summary

  • Add --coverage.provider=istanbul to individual package coverage scripts for independent execution
  • Remove redundant coverage CLI options from root script to avoid duplicate provider error

Test plan

  • Run pnpm run coverage from root
  • Run pnpm run coverage from individual packages (e.g., packages/stripe)

Summary by cubic

Added --coverage.provider=istanbul to each package’s coverage script and removed provider/reporter flags from the root coverage script. This standardizes coverage and prevents duplicate provider errors when running coverage from the root or individual packages.

Written for commit 52e8979534. 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/7262 **Author:** [@sukvvon](https://github.com/sukvvon) **Created:** 1/11/2026 **Status:** ✅ Merged **Merged:** 1/11/2026 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `chore/vitest-coverage-scripts` --- ### 📝 Commits (5) - [`c74dd7f`](https://github.com/better-auth/better-auth/commit/c74dd7ff185be8ca8cffe9afe3fb097b0861175a) chore(*/package.json): add '--coverage.provider=istanbul' to coverage scripts - [`e329423`](https://github.com/better-auth/better-auth/commit/e329423a98a21eb57ac180d8433213f897d48ff4) chore(package.json): remove redundant coverage CLI options from root script - [`c08fe5a`](https://github.com/better-auth/better-auth/commit/c08fe5adeb0f10cafd1217efedd3b48f71937f76) Merge branch 'canary' into chore/vitest-coverage-scripts - [`49d0c53`](https://github.com/better-auth/better-auth/commit/49d0c53423f327c62071a77ea7e9e1c84a5a4719) Merge branch 'canary' into chore/vitest-coverage-scripts - [`52e8979`](https://github.com/better-auth/better-auth/commit/52e89795348282dd98bff430c4d7657a3d74f653) Merge branch 'canary' into chore/vitest-coverage-scripts ### 📊 Changes **10 files changed** (+10 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+1 -1) 📝 `packages/better-auth/package.json` (+1 -1) 📝 `packages/cli/package.json` (+1 -1) 📝 `packages/core/package.json` (+1 -1) 📝 `packages/expo/package.json` (+1 -1) 📝 `packages/passkey/package.json` (+1 -1) 📝 `packages/scim/package.json` (+1 -1) 📝 `packages/sso/package.json` (+1 -1) 📝 `packages/stripe/package.json` (+1 -1) 📝 `test/package.json` (+1 -1) </details> ### 📄 Description ## Summary - Add `--coverage.provider=istanbul` to individual package coverage scripts for independent execution - Remove redundant coverage CLI options from root script to avoid duplicate provider error ## Test plan - [x] Run `pnpm run coverage` from root - [x] Run `pnpm run coverage` from individual packages (e.g., `packages/stripe`) <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Added --coverage.provider=istanbul to each package’s coverage script and removed provider/reporter flags from the root coverage script. This standardizes coverage and prevents duplicate provider errors when running coverage from the root or individual packages. <sup>Written for commit 52e89795348282dd98bff430c4d7657a3d74f653. 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-03-13 13:27:01 -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#7182
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?