@shivaedev/create-app 0.7.0 → 0.8.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 +13 -0
- package/README.md +0 -11
- package/package.json +4 -5
- package/template.json +1 -1
- package/docs/north-star.md +0 -7
- package/docs/roadmap.md +0 -18
package/docs/north-star.md
DELETED
|
@@ -1,7 +0,0 @@
|
|
|
1
|
-
# One command to a running app
|
|
2
|
-
|
|
3
|
-
New applications should start with the same small, working example that Platform maintains and tests. A newcomer should not need to understand workspace dependency protocols or repository-specific configuration before seeing their application run.
|
|
4
|
-
|
|
5
|
-
The command writes only into an absent or empty folder, names the application, generates its local environment, installs its dependencies and prints the development steps. The starter owns the application's files, database preparation and published-version manifest; packaging takes a snapshot of that source. Generated files are package artifacts, never a second checked-in template.
|
|
6
|
-
|
|
7
|
-
Preserving existing user files takes precedence over convenience. Real generated-app checks against npm and PostgreSQL take precedence over fast scaffolding tests. Keep the interface to the folder argument and normal CLI help and version output. Production configuration, deployment and releases belong to the application and maintainer.
|
package/docs/roadmap.md
DELETED
|
@@ -1,18 +0,0 @@
|
|
|
1
|
-
# Roadmap
|
|
2
|
-
|
|
3
|
-
## Built
|
|
4
|
-
|
|
5
|
-
- A folder argument creates and installs the starter with exact published Platform versions.
|
|
6
|
-
- Packing snapshots `examples/starter` without local dependencies, build output, lockfiles or environment secrets.
|
|
7
|
-
- Existing nonempty folders are refused before any write or install.
|
|
8
|
-
- Each generated app has a git-ignored local environment with a fresh authentication secret and app-specific development and test database URLs.
|
|
9
|
-
- A generated app has its own named README, framework guidance and linked `CLAUDE.md`, matching example database URLs, and normal non-secret file permissions without template maintenance files or names.
|
|
10
|
-
- The generated app prepares both local databases before development and loads its test database URL from the local environment.
|
|
11
|
-
- The published-starter check runs the packed command's output through typecheck, build and PostgreSQL/authenticated HTTP tests.
|
|
12
|
-
- A generated app gets an initial Git commit outside an enclosing repository when Git is available; `--no-git` opts out.
|
|
13
|
-
- Setup installs dependencies and Quality's hook after repository initialization; the initial commit runs lint and typecheck, and `pnpm ready` runs the full local gate.
|
|
14
|
-
- A generated app includes GitHub Actions checks against PostgreSQL and Railway build, migration, start and health-check configuration.
|
|
15
|
-
|
|
16
|
-
## Open questions
|
|
17
|
-
|
|
18
|
-
No open generator decisions.
|