create-kerf-component 2.0.1 → 3.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-kerf-component",
-  "version": "2.0.1",
+  "version": "3.0.0",
   "description": "Scaffold a publishable kerf component package that already follows kerf's hard packaging rules.",
   "type": "module",
   "license": "MIT",

package/template/README.md

@@ -44,6 +44,11 @@ have to:
   string-builders; emit `data-action` hooks and let the host wire events with
   `delegate()` (see `wireCounter`), which returns a disposer.
 - **Build emits ESM + `.d.ts`; `tsconfig` sets `jsxImportSource: "kerfjs"`.**
+- **Never import `kerfjs/dev`.** kerf's dev diagnostics install global hooks, so
+  installing them is the consuming *app's* call, not a library's — the app
+  writes `if (import.meta.env.DEV) await import('kerfjs/dev')` in its own entry.
+  To get the diagnostics while developing this package, add that line to your own
+  test harness or demo page instead (it belongs to the harness, not to `src/`).
 
 ## Publish
 

package/template/package.json

@@ -30,6 +30,6 @@
   "devDependencies": {
     "kerfjs": "^0.15.0",
     "tsup": "^8",
-    "typescript": "^5"
+    "typescript": "^5 || ^6"
   }
 }