@better-auth/core 1.3.32 → 1.3.33
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.turbo/turbo-build.log +2 -2
- package/package.json +1 -1
package/.turbo/turbo-build.log
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
|
|
2
|
-
> @better-auth/core@1.3.
|
|
2
|
+
> @better-auth/core@1.3.33 build /home/runner/work/better-auth/better-auth/packages/core
|
|
3
3
|
> unbuild --clean
|
|
4
4
|
|
|
5
5
|
[info] Building core
|
|
@@ -8,8 +8,8 @@ Generated an empty chunk: "index".
|
|
|
8
8
|
Generated an empty chunk: "db/adapter/index".
|
|
9
9
|
Generated an empty chunk: "index".
|
|
10
10
|
Generated an empty chunk: "db/adapter/index".
|
|
11
|
-
"bun:sqlite" is imported by "src/types/init-options.ts", but could not be resolved – treating it as an external dependency.
|
|
12
11
|
"node:sqlite" is imported by "src/types/init-options.ts", but could not be resolved – treating it as an external dependency.
|
|
12
|
+
"bun:sqlite" is imported by "src/types/init-options.ts", but could not be resolved – treating it as an external dependency.
|
|
13
13
|
Export "ProviderOptions" of module "src/oauth2/oauth-provider.ts" was reexported through module "src/oauth2/index.ts" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
|
|
14
14
|
Either change the import in "src/oauth2/create-authorization-url.ts" to point directly to the exporting module or reconfigure "output.manualChunks" to ensure these modules end up in the same chunk.
|
|
15
15
|
Export "ProviderOptions" of module "src/oauth2/oauth-provider.ts" was reexported through module "src/oauth2/index.ts" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
|