@shivaedev/create-app 0.34.0 → 0.36.0
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/CHANGELOG.md +38 -0
- package/README.md +1 -1
- package/dist/cli.js +27 -27
- package/dist/pack.js +2 -1
- package/dist/pack.js.map +1 -1
- package/dist/updateApp.d.ts.map +1 -1
- package/dist/updateApp.js +17 -10
- package/dist/updateApp.js.map +1 -1
- package/dist/updateChecks.js +1 -1
- package/dist/updateChecks.js.map +1 -1
- package/package.json +4 -4
- package/src/pack.ts +2 -1
- package/src/updateApp.ts +18 -10
- package/src/updateChecks.ts +1 -1
- package/template.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,43 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.36.0 - 2026-11-02
|
|
4
|
+
|
|
5
|
+
### Added
|
|
6
|
+
|
|
7
|
+
- Add `redactBrowserText` to mask quoted browser literals, including escaped quotes and multiline content, while preserving diagnostic shape and the existing server text policy.
|
|
8
|
+
- Add opt-in `browserErrors` settings for an Error log per report, signed-in `user.id` attribution and session enforcement. The starter enables all three.
|
|
9
|
+
|
|
10
|
+
### Fixed
|
|
11
|
+
|
|
12
|
+
- Mask browser report messages and stacks before they reach diagnostic sinks and record reports at Error severity.
|
|
13
|
+
- Apply starter updates to apps inside enclosing Git repositories while preserving sibling files and unrelated staged changes. Keep the generation record unchanged when a nonempty starter delta applies no changes.
|
|
14
|
+
- Generated notes apps show an alert when adding or saving a note defects, keep the draft, and handle delete completion in the note's own action.
|
|
15
|
+
- Generated Railway workers receive shared `RESEND_API_KEY`, `EMAIL_FROM` and `PUBLIC_URL` settings. Production workers require an explicit email sender at startup; deployment instructions describe queued auth email delivery and the worker's production settings.
|
|
16
|
+
- Generated starter stories settle through screen pending signals and completed HTTP/live results instead of status markup or timed connection sampling. Remove the redundant third-party session lifecycle fixture and its teardown delays.
|
|
17
|
+
|
|
18
|
+
## 0.35.0 - 2026-11-01
|
|
19
|
+
|
|
20
|
+
### Added
|
|
21
|
+
|
|
22
|
+
- Enforce `imports/admin-paths`: report admin-only source files outside an `admin/` path and admin files reached by member code, naming the destination folder. Follow production imports within each source tree while allowing registration composition and shared member dependencies.
|
|
23
|
+
- Admit per-key budgets through `@shivaedev/rate-limit`, with an Effect-clock memory store, a PostgreSQL adapter, and typed `TooManyRequests` carrying a retry time.
|
|
24
|
+
- Include rate limiting in Platform and demonstrate a per-user note creation budget in generated applications.
|
|
25
|
+
- Send transactional email through a Resend-backed Mailer or development log, with typed message queues, job-id idempotency, backoff and provider-timed rate-limit retries.
|
|
26
|
+
- Read delivered messages and one-time links through a fake Resend inbox in stories.
|
|
27
|
+
- Include the email package in Platform for applications, including the starter's queued authentication emails.
|
|
28
|
+
|
|
29
|
+
### Fixed
|
|
30
|
+
|
|
31
|
+
- Report production imports of the `@effect/platform-node` barrel with module subpaths that avoid loading optional integrations such as redis.
|
|
32
|
+
- Recognize native Effect `catchTags` record keys regardless of the handler body while retaining diagnostics for actual nested component and hook factories.
|
|
33
|
+
- Keep a constant's matching filename valid when the constant becomes private.
|
|
34
|
+
- Name each conflicting fix and format pass's file and line/column range when `quality fix` cannot settle.
|
|
35
|
+
- Use Node platform module subpaths in package runtimes and commands instead of loading the barrel.
|
|
36
|
+
|
|
37
|
+
### Breaking
|
|
38
|
+
|
|
39
|
+
- Generated apps keep shared declarations outside the admin-only tree. Migrate custom `ReadStatistics` imports from `#admin/ReadStatistics.ts` to `#ReadStatistics.ts`, and custom `AdminNavigation` type imports from `#client/admin/Shell.tsx` to `#client/AdminNavigation.ts`.
|
|
40
|
+
|
|
3
41
|
## 0.34.0 - 2026-11-01
|
|
4
42
|
|
|
5
43
|
### Added
|
package/README.md
CHANGED
|
@@ -50,7 +50,7 @@ Run `pnpm run setup` after cloning the generated repository to install dependenc
|
|
|
50
50
|
|
|
51
51
|
### Take starter updates
|
|
52
52
|
|
|
53
|
-
Run `pnpm dlx @shivaedev/create-app@latest update` in a generated app with a clean
|
|
53
|
+
Run `pnpm dlx @shivaedev/create-app@latest update` in a generated app with a clean app directory in Git to take later starter changes. Apps inside an enclosing repository receive the changes within their own directory; sibling files and unrelated staged changes stay untouched. Only the app directory must be clean. A nonempty starter delta that applies no changes fails without advancing `.create-app.json`. The command reads `.create-app.json`, downloads the recorded generator’s starter and uses Git’s three-way merge to replay its changes against the current starter; app edits survive, deleted files stay deleted, and conflicts are listed and left for you to resolve. Once the starter changes apply, including a merge with conflicts, `.create-app.json` records the current generator version. The command runs `pnpm install` and the app’s `pnpm run typecheck`, lists every non-ignored file with conflict markers and any unresolved Git conflicts, and exits nonzero while those or either check’s failures remain. Resolve the reported problems and rerun install and typecheck before committing. If pnpm reports a trust downgrade, the command preserves the rejected package and version and gives `pnpm update --depth Infinity` to re-resolve transitive dependencies under the existing trust policy; an exact manifest or catalog pin must first be changed to a trusted version. An update adds the admin Users registration and route to an app that lacks them, and lists conflicts where the app customized those parts.
|
|
54
54
|
|
|
55
55
|
### Reuse the generator
|
|
56
56
|
|