@reckona/create-mreact-app 0.0.14 → 0.0.15
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/README.md +1 -1
- package/dist/index.js +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -40,7 +40,7 @@ for API Gateway HTTP API v2 and Lambda Function URL payload format 2.0.
|
|
|
40
40
|
|
|
41
41
|
For AWS Lambda production apps, add packages imported by loaders, middleware, route handlers, metadata, server actions, or their app-local helper modules to `importPolicy.allowedPackages` in the generated `src/lambda.ts`.
|
|
42
42
|
|
|
43
|
-
Package Lambda deployments from a minimal asset directory, not the full project root. The generated `docs/deploy/aws-lambda.md` shows a `prepare-lambda-asset.sh` example that copies `.mreact/`, the bundled handler, manifests, lockfiles, and production `node_modules` into `.lambda/` so CDK/SAM/serverless assets stay below AWS's 250 MB unzipped deployment package limit. Generated Lambda projects build with `mreact-router build --target=node`, keeping Cloudflare Workers route modules out of Node-only artifacts. The Lambda adapter treats `outDir` as read-only and materializes runtime files under `/tmp` by default, so `.mreact/` can stay inside the deployed package; handler creation also starts a background preload for built runtime modules, route modules, and route metadata so route-specific bundling can move out of the first matched request on warmable runtimes. For pnpm projects, the generated script uses `--config.node-linker=hoisted` and includes symlink and actual-file-byte checks because pnpm's default isolated linker can create Lambda artifacts that package larger than `du` suggests.
|
|
43
|
+
Package Lambda deployments from a minimal asset directory, not the full project root. The generated `docs/deploy/aws-lambda.md` shows a `prepare-lambda-asset.sh` example that copies `.mreact/`, the bundled handler, manifests, lockfiles, and production `node_modules` into `.lambda/` so CDK/SAM/serverless assets stay below AWS's 250 MB unzipped deployment package limit. Generated Lambda projects build with `mreact-router build --target=node`, keeping Cloudflare Workers route modules out of Node-only artifacts and storing compiled server route artifacts in `.mreact/server/server-modules/*.json` instead of one large server manifest. The Lambda adapter treats `outDir` as read-only and materializes runtime files under `/tmp` by default, so `.mreact/` can stay inside the deployed package; handler creation also starts a background preload for built runtime modules, route modules, and route metadata so route-specific bundling can move out of the first matched request on warmable runtimes. For pnpm projects, the generated script uses `--config.node-linker=hoisted` and includes symlink and actual-file-byte checks because pnpm's default isolated linker can create Lambda artifacts that package larger than `du` suggests.
|
|
44
44
|
|
|
45
45
|
Use `--src-dir` to generate a larger-app layout:
|
|
46
46
|
|
package/dist/index.js
CHANGED
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
import { mkdir, readdir, writeFile } from "node:fs/promises";
|
|
2
2
|
import { basename, dirname, join } from "node:path";
|
|
3
3
|
const internalPackageVersions = {
|
|
4
|
-
"@reckona/mreact": "^0.0.
|
|
5
|
-
"@reckona/mreact-reactive-core": "^0.0.
|
|
6
|
-
"@reckona/mreact-router": "^0.0.
|
|
4
|
+
"@reckona/mreact": "^0.0.15",
|
|
5
|
+
"@reckona/mreact-reactive-core": "^0.0.15",
|
|
6
|
+
"@reckona/mreact-router": "^0.0.15",
|
|
7
7
|
};
|
|
8
8
|
const typescriptVersion = "^6.0.3";
|
|
9
9
|
const tailwindVersion = "^4.3.0";
|