create-bakery 1.0.2 → 1.1.1
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/package.json +1 -1
- package/src/template.ts +3 -3
package/package.json
CHANGED
package/src/template.ts
CHANGED
|
@@ -370,7 +370,7 @@ ${pluginSection}
|
|
|
370
370
|
* The three JSX options are repeated here on purpose, and removing them breaks
|
|
371
371
|
* every page in the generated app.
|
|
372
372
|
*
|
|
373
|
-
* `@bakery-framework/core/tsconfig.
|
|
373
|
+
* `@bakery-framework/core/tsconfig.server.json` already sets them, and `tsc` picks them up
|
|
374
374
|
* from there — but **Bun's runtime does not follow `extends` into a package
|
|
375
375
|
* specifier**, only a relative path. So at runtime the app is transpiled with
|
|
376
376
|
* Bun's default automatic JSX runtime instead of Bakery's classic
|
|
@@ -391,8 +391,8 @@ function tsconfig(orm: boolean): string {
|
|
|
391
391
|
.join(',\n')
|
|
392
392
|
|
|
393
393
|
return `{
|
|
394
|
-
"$comment": "The three jsx* options are also set by @bakery-framework/core/tsconfig.
|
|
395
|
-
"extends": "@bakery-framework/core/tsconfig.
|
|
394
|
+
"$comment": "The three jsx* options are also set by @bakery-framework/core/tsconfig.server.json, and tsc reads them from there — but Bun's runtime does not follow 'extends' into a package specifier, only a relative path. Without them here, every .tsx page fails at runtime with \\"Cannot find module 'react/jsx-dev-runtime'\\" while typecheck stays clean. Keep them.",
|
|
395
|
+
"extends": "@bakery-framework/core/tsconfig.server.json",
|
|
396
396
|
"compilerOptions": {
|
|
397
397
|
"jsx": "react",
|
|
398
398
|
"jsxFactory": "createElement",
|