clone

a deno framework for local-first web apps that open instantly, work offline and sync when users choose

feat(template): keep generic static-deploy scaffolding in generated projects

Dami committed 5fd3178
Restore the deploy/deploy:create tasks to the template deno.json. They carry
the reusable config a lofi static PWA needs on Deno Deploy — build, then push
dist/ as the deploy root (static, no remote build, no src/app.ts misdetection)
— with no org/app baked in. A fresh project just supplies --org/--app.

Only the reference-specific deploy field (felinestatemachine/lofi-dev) stays
removed. Document the flow in the generated and reference READMEs.
commit
5fd31784493f3dfd1bfc208192827dbe7f5f8b57
parent
02f2e8c760e2f20155952cb2aa68257044ee079a
author
Dami <dami.etoile@gmail.com>
4 files changed, +20 -4
Mapps/reference/README.md8++++++--
Mapps/reference/deno.json2++
Mpackage/create_core.ts10++++++++++
Mpackage/testdata/starter.snapshot.json4++--
M apps/reference/README.md +6 -2
M apps/reference/deno.json +2 -0
M package/create_core.ts +10 -0
M package/testdata/starter.snapshot.json +2 -2