Node.js repositories

Collection of runnable Node.js projects. Every project lives under templates/:

hostinger-templates/
├── templates/
│   └── <repository-id>/
├── skills/
├── versions/catalog.json
└── templates.json

Repository catalog

templates.json is the source of truth for projects in this collection. Its templates array lists every finished project. Add one entry when a project is created.

Each entry can contain these fields:

• id and name
• summary and description
• bucket, categories, and whoItsFor
• demoUrl
• classification: categories, use cases, and frameworks
• features: at most 4 verified feature IDs, names, and descriptions
• technology: languages, frameworks, styling, data strategy, and deployment
• compatibility: runtimes and supported versions
• media: thumbnail and preview metadata
• searchTerms

Project paths use templates/<id>/, where the directory name matches the catalog id.

Adding a project

Follow skills/create-repository/SKILL.md. It defines the creation workflow; skills/create-repository/RULES.md defines constraints every project must follow.

Bumping dependencies

Templates stay standalone (own package.json and lockfile). Shared pins live in versions/catalog.json. To move a package across every template on the same major:

npm run bump -- nuxt 4.5.1

Different majors are skipped unless you pass --major. Use --dry-run to preview. Update templates.json compatibility and README prerequisites by hand when engines change. Dependabot still opens grouped security PRs; this command is for catalog-led bumps Dependabot will not fan out (same advisory, other directories).

Translations

Template summaries, descriptions and category labels are shown in hPanel in English, straight from templates.json — there is no translation pipeline for the v1 release.