@typestyles/build-runner 0.5.0 → 0.5.2

package/dist/index.cjs

@@ -540,6 +540,25 @@ async function runTypestylesBuild({
     format: "cjs",
     target: "node18",
     external: ["typestyles"],
+    // Style registration calls (styles.component/class, createTypeStyles) are
+    // side-effect-only: the CSS they register into the global registry is the
+    // point, regardless of whether the returned classname function is ever
+    // read. esbuild's default tree shaking doesn't know that, so any
+    // consumer module reached only through an unread namespace/barrel import
+    // (or a package marked "sideEffects": false) can have its registration
+    // calls silently dropped as "unused". Disable tree shaking here so every
+    // registration in the extraction graph survives.
+    treeShaking: false,
+    // `treeShaking: false` only stops esbuild from pruning declarations
+    // *within* an already-included module. It's a separate esbuild behavior
+    // by the treeShaking option — that drops a plain bare import entirely
+    // (`import './some-lib'` with no binding at all) when it resolves to a
+    // module/package marked "sideEffects": false, before that module is ever
+    // considered for inclusion. A real extraction entry is exactly this
+    // shape: several side-effect-only imports, any one of which may point at
+    // a (correctly) tree-shakeable component library. Ignore both kinds of
+    // annotation so every import in the extraction graph is included.
+    ignoreAnnotations: true,
     stdin: {
       contents: importLines,
       resolveDir: root,

package/dist/index.js

@@ -494,6 +494,25 @@ async function runTypestylesBuild({
     format: "cjs",
     target: "node18",
     external: ["typestyles"],
+    // Style registration calls (styles.component/class, createTypeStyles) are
+    // side-effect-only: the CSS they register into the global registry is the
+    // point, regardless of whether the returned classname function is ever
+    // read. esbuild's default tree shaking doesn't know that, so any
+    // consumer module reached only through an unread namespace/barrel import
+    // (or a package marked "sideEffects": false) can have its registration
+    // calls silently dropped as "unused". Disable tree shaking here so every
+    // registration in the extraction graph survives.
+    treeShaking: false,
+    // `treeShaking: false` only stops esbuild from pruning declarations
+    // *within* an already-included module. It's a separate esbuild behavior
+    // by the treeShaking option — that drops a plain bare import entirely
+    // (`import './some-lib'` with no binding at all) when it resolves to a
+    // module/package marked "sideEffects": false, before that module is ever
+    // considered for inclusion. A real extraction entry is exactly this
+    // shape: several side-effect-only imports, any one of which may point at
+    // a (correctly) tree-shakeable component library. Ignore both kinds of
+    // annotation so every import in the extraction graph is included.
+    ignoreAnnotations: true,
     stdin: {
       contents: importLines,
       resolveDir: root,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typestyles/build-runner",
-  "version": "0.5.0",
+  "version": "0.5.2",
   "description": "Shared module execution utilities for typestyles build integrations",
   "type": "module",
   "main": "./dist/index.cjs",
@@ -29,7 +29,8 @@
     "eslint": "^9.39.2",
     "tsup": "^8.0.0",
     "typescript": "^5.4.0",
-    "vitest": "^3.0.0"
+    "vitest": "^3.0.0",
+    "typestyles": "0.8.2"
   },
   "license": "Apache-2.0",
   "repository": {