Template scaffolder + config schema#9
Open
miguelrisero wants to merge 2 commits into
Open
Conversation
`npm run new -- <name> <type>` (or interactive) scaffolds a slug-named starter for any of the 7 types with the base-path wiring and a $schema-referenced template.config.json where needed — so contributors don't reverse-engineer the conventions. template.config.schema.json gives editor validation/autocomplete for custom + node-functions configs.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack 5 of 5 (base:
feat/seo-and-funnel). Council DX — turn template creation into a paved road.npm run new -- <name> <type>(or interactivenpm run new) scaffolds a starter for any of the 7 types (static,vite,next,nuxt,nuxt-server,custom,node-functions): validates the slug, wires the base path, and stamps a$schema-referencedtemplate.config.jsonwhere needed. Closes the "only 2 of 7 types have examples / conventions are tribal knowledge" gap.template.config.schema.json— JSON Schema for the per-project config (type enum,dashboard,functions,crons,noindex, …). Referenced via"$schema"so editors validate + autocomplete it.Verified: scaffolder rejects bad names, scaffolds + builds a
statictemplate, and emits correctnextfiles (cleaned up after testing).npm test(13) green.