@csszyx/types 0.9.10 → 0.10.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/config.d.cts CHANGED
@@ -334,6 +334,27 @@ type PartialCsszyxConfig = {
334
334
  * marker and would otherwise hit the AST budget guard.
335
335
  */
336
336
  exclude?: FilePattern | FilePattern[];
337
+ /**
338
+ * Opt workspace packages under `/packages/` into compilation.
339
+ *
340
+ * csszyx hard-ignores `/packages/` by default because published libraries
341
+ * are expected to ship pre-extracted CSS. In a monorepo, however, a
342
+ * design-system package is first-class source the developer authors, so its
343
+ * `sz` props must be compiled like app code. List the package directory
344
+ * names here (e.g. `['vui']`) to compile `**\/packages/<name>/**`. Only the
345
+ * `/packages/` rule is relaxed — `node_modules` and `.next` stay ignored.
346
+ */
347
+ compilePackages?: string[];
348
+ /**
349
+ * Warn when, inside a monorepo, the Tailwind entry imports `tailwindcss`
350
+ * without scoping its content detection (no `source(none)` / `source(...)` /
351
+ * `@source not`). Unscoped, Tailwind v4 climbs to the workspace root and
352
+ * scans sibling packages + docs (`.md`/`.mdx`/`.txt` are not ignored),
353
+ * which can generate phantom or broken `url()` classes and fail the build.
354
+ * The warning prints the one-time fix; set `false` to silence it when a
355
+ * broad scan is intentional. Defaults to `true`.
356
+ */
357
+ contentScopeCheck?: boolean;
337
358
  development?: Partial<DevelopmentConfig>;
338
359
  production?: Partial<ProductionConfig>;
339
360
  build?: Partial<BuildConfig>;
package/dist/config.d.mts CHANGED
@@ -334,6 +334,27 @@ type PartialCsszyxConfig = {
334
334
  * marker and would otherwise hit the AST budget guard.
335
335
  */
336
336
  exclude?: FilePattern | FilePattern[];
337
+ /**
338
+ * Opt workspace packages under `/packages/` into compilation.
339
+ *
340
+ * csszyx hard-ignores `/packages/` by default because published libraries
341
+ * are expected to ship pre-extracted CSS. In a monorepo, however, a
342
+ * design-system package is first-class source the developer authors, so its
343
+ * `sz` props must be compiled like app code. List the package directory
344
+ * names here (e.g. `['vui']`) to compile `**\/packages/<name>/**`. Only the
345
+ * `/packages/` rule is relaxed — `node_modules` and `.next` stay ignored.
346
+ */
347
+ compilePackages?: string[];
348
+ /**
349
+ * Warn when, inside a monorepo, the Tailwind entry imports `tailwindcss`
350
+ * without scoping its content detection (no `source(none)` / `source(...)` /
351
+ * `@source not`). Unscoped, Tailwind v4 climbs to the workspace root and
352
+ * scans sibling packages + docs (`.md`/`.mdx`/`.txt` are not ignored),
353
+ * which can generate phantom or broken `url()` classes and fail the build.
354
+ * The warning prints the one-time fix; set `false` to silence it when a
355
+ * broad scan is intentional. Defaults to `true`.
356
+ */
357
+ contentScopeCheck?: boolean;
337
358
  development?: Partial<DevelopmentConfig>;
338
359
  production?: Partial<ProductionConfig>;
339
360
  build?: Partial<BuildConfig>;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@csszyx/types",
3
- "version": "0.9.10",
3
+ "version": "0.10.0",
4
4
  "description": "TypeScript definitions for csszyx",
5
5
  "keywords": [
6
6
  "csszyx",
@@ -57,7 +57,7 @@
57
57
  "@types/node": "^20.11.0",
58
58
  "typescript": "^6.0.3",
59
59
  "unbuild": "^3.6.1",
60
- "@csszyx/compiler": "0.9.10"
60
+ "@csszyx/compiler": "0.10.0"
61
61
  },
62
62
  "sideEffects": false,
63
63
  "engines": {