create-packkit 1.4.0 → 1.4.1

package/README.md

@@ -80,6 +80,13 @@ Packkit is a pure `config → { files }` **core** that runs in both Node and the
 
 Both drive from one options schema ([`src/core/options.js`](src/core/options.js)), so the CLI and the web page always stay in sync.
 
+## Staying fresh
+
+Two GitHub Actions keep the templates honest:
+
+- **Dependency freshness** — a weekly check flags any version Packkit writes into generated projects that's fallen a major behind (versions Dependabot can't see), and opens an issue.
+- **Integration** — on any change to generation logic or a template dependency, it generates every preset, installs it, and runs its real checks (build/test/lint, and actually starts services) — so an update can't silently break the projects you'd get.
+
 ## License
 
 [MIT](LICENSE) © DanMat

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-packkit",
-  "version": "1.4.0",
+  "version": "1.4.1",
   "description": "Highly configurable scaffolder for modern npm packages and CLIs — pick your stack (TS/JS, bundler, tests, linter, CI, releases) from a CLI or a web configurator.",
   "type": "module",
   "bin": {
@@ -25,6 +25,7 @@
     "start": "node bin/cli.js",
     "test": "node --test",
     "check:deps": "node scripts/check-template-deps.mjs",
+    "integration": "node scripts/integration.mjs",
     "build:web": "esbuild src/core/index.js --bundle --format=esm --outfile=docs/packkit-core.js"
   },
   "repository": {

package/src/core/features/bundler.js

@@ -46,6 +46,9 @@ export default {
       pkg.scripts.build = tool;
       pkg.scripts.dev = `${tool} --watch`;
       pkg.devDependencies = { [tool]: tool === 'tsup' ? '^8.0.0' : '^0.6.0' };
+      // tsup/tsdown resolve `typescript` even for plain-JS builds; TS projects
+      // already get it from the typescript feature.
+      if (!cfg.isTs) pkg.devDependencies.typescript = '^5.5.0';
     } else if (cfg.bundler === 'unbuild') {
       files['build.config.ts'] = unbuildConfig(cfg);
       pkg.scripts.build = 'unbuild';