[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@seamless-auth/core@0.20.1

Patch Changes

• 8ff942d: Depend on @types/jsonwebtoken at runtime instead of as a dev dependency. The published declarations import JwtPayload from jsonwebtoken (for example in verifyCookieJwt), so consumers without their own copy got TS7016 under skipLibCheck: false and an any payload type otherwise.

@seamless-auth/express@0.20.1

Patch Changes

• 8ff942d: Publish declarations that resolve under moduleResolution: "NodeNext" and "Node16". Relative imports in the shipped .d.ts files now carry explicit .js extensions. Consumers on NodeNext previously could not resolve them, so the exported functions typed as any (hidden by skipLibCheck). Runtime output is unchanged.
• f0d50f7: Ship the Express.Request augmentation. req.user (set by requireAuth) and req.cookiePayload (set by createEnsureCookiesMiddleware) now typecheck in a consumer that imports the package, without declaring the augmentation itself. It previously lived in an ambient .d.ts that tsc never copied into dist.
• dd5c0e5: The README examples read the service secret from SEAMLESS_SERVICE_TOKEN instead of SERVICE_SECRET. The auth server still reads API_SERVICE_TOKEN; both hold the same value. The adapters read no environment variables, so nothing changes at runtime.
• Updated dependencies [8ff942d]
  • @seamless-auth/core@0.20.1

@seamless-auth/fastify@0.11.2

Patch Changes

• 8ff942d: Publish declarations that resolve under moduleResolution: "NodeNext" and "Node16". Relative imports in the shipped .d.ts files now carry explicit .js extensions. Consumers on NodeNext previously could not resolve them, so the exported functions typed as any (hidden by skipLibCheck). Runtime output is unchanged.
• f0d50f7: Load the FastifyRequest augmentation (request.user, request.cookiePayload) from the package entry through an import that resolves under moduleResolution: "NodeNext". Consumers on NodeNext previously lost it because the entry reached it only through an extensionless relative import.
• dd5c0e5: The README examples read the service secret from SEAMLESS_SERVICE_TOKEN instead of SERVICE_SECRET. The auth server still reads API_SERVICE_TOKEN; both hold the same value. The adapters read no environment variables, so nothing changes at runtime.
• Updated dependencies [8ff942d]
  • @seamless-auth/core@0.20.1

@seamless-auth/nextjs@0.4.1

Patch Changes

• 8ff942d: Publish declarations that resolve under moduleResolution: "NodeNext" and "Node16". Relative imports in the shipped .d.ts files now carry explicit .js extensions. Consumers on NodeNext previously could not resolve them, so the exported functions typed as any (hidden by skipLibCheck). Runtime output is unchanged.
• dd5c0e5: The README examples read the service secret from SEAMLESS_SERVICE_TOKEN instead of SERVICE_SECRET. The auth server still reads API_SERVICE_TOKEN; both hold the same value. The adapters read no environment variables, so nothing changes at runtime.
• Updated dependencies [8ff942d]
  • @seamless-auth/core@0.20.1