@homepages/template-kit 0.0.1 → 0.2.0

package/tsconfig.json

@@ -1,18 +1,7 @@
 {
+  "extends": "./tsconfig.base.json",
   "compilerOptions": {
-    "target": "ES2022",
-    "module": "ESNext",
-    "moduleResolution": "Bundler",
-    "lib": ["ES2022", "DOM"],
-    "jsx": "react-jsx",
-    "strict": true,
-    "noUncheckedIndexedAccess": true,
-    "esModuleInterop": true,
-    "skipLibCheck": true,
-    "isolatedModules": true,
-    "resolveJsonModule": true,
-    "forceConsistentCasingInFileNames": true,
     "noEmit": true
   },
-  "exclude": ["node_modules", "dist"]
+  "exclude": ["node_modules", "dist", ".tmp-consumer"]
 }

package/dist/src-dZr5N30y.js

@@ -1,35 +0,0 @@
-import { jsx } from "react/jsx-runtime";
-
-//#region package.json
-var version = "0.0.1";
-
-//#endregion
-//#region src/kit-smoke.tsx
-/**
-* Boundary probe, not authoring surface. Its only job is to make the package
-* boundary testable: React stays a peer, types resolve, and Tailwind's
-* cross-package @source scan reaches this file's compiled output.
-* Removed when the real contract primitives land.
-*/
-function KitSmoke({ label }) {
-	return /* @__PURE__ */ jsx("span", {
-		className: "bg-kit-smoke uppercase tracking-[0.4275em]",
-		children: label
-	});
-}
-
-//#endregion
-//#region src/index.ts
-/**
-* The published version of this kit.
-*
-* Read from package.json and inlined at build time, so it cannot drift: changesets
-* owns package.json's version, and a hardcoded constant here would have to be
-* hand-edited on every release — on a branch changesets force-pushes, which would
-* silently discard the edit. `dist/cli.js --version` is asserted against
-* package.json to prove the inlining actually happened.
-*/
-const KIT_VERSION = version;
-
-//#endregion
-export { KitSmoke as n, KIT_VERSION as t };