@bamboocss/generator 1.30.0 → 1.31.0

package/dist/index.d.cts

@@ -146,4 +146,33 @@ declare class Generator extends Context {
  */
 declare function getThemeCss(ctx: Context, themeName: string): string;
 //#endregion
-export { Generator, SplitCssArtifact, SplitCssResult, getThemeCss };
+//#region src/artifacts/js/package-json.d.ts
+/**
+ * The entry points this output offers, and — where it is resolved as a package — the only
+ * paths into it.
+ *
+ * Two things this buys, and one it does not.
+ *
+ * It makes the entry points resolve under `node16`/`nodenext`. Without a map, those modes do
+ * no directory-index lookup, so `styled-system/tokens` does not resolve at all and the
+ * artifact has to be spelled `styled-system/tokens/index.mjs` — a workaround
+ * `token-references.ts` still has to recognise because people write it. Declaring `./tokens`
+ * is what makes the ordinary spelling work.
+ *
+ * It states the boundary. `css/merge-css`, `css/utilities`, `tokens/tokens` and `helpers`
+ * exist to be imported by the modules beside them, not by an app; a relative import inside
+ * the package is unaffected by this map, an external one now fails.
+ *
+ * What it does not do is enforce that against the common setup. The generated directory
+ * usually lives in the project and is reached through a `paths` alias —
+ * `"styled-system/*": ["./styled-system/*"]` — and a `paths` mapping resolves straight to the
+ * filesystem, so no `exports` map is consulted. There is nothing this file can do about that;
+ * the enforcement lands where the output is consumed as a real package, which is the
+ * component-library layout `emit-pkg` produces.
+ *
+ * `./types` carries no runtime target because the directory holds only declarations. A type
+ * import resolves; a value import fails, which is the truth about it.
+ */
+declare function generatePackageExports(ctx: Context, base?: string): Record<string, unknown>;
+//#endregion
+export { Generator, SplitCssArtifact, SplitCssResult, generatePackageExports, getThemeCss };

package/dist/index.d.mts

@@ -146,4 +146,33 @@ declare class Generator extends Context {
  */
 declare function getThemeCss(ctx: Context, themeName: string): string;
 //#endregion
-export { Generator, SplitCssArtifact, SplitCssResult, getThemeCss };
+//#region src/artifacts/js/package-json.d.ts
+/**
+ * The entry points this output offers, and — where it is resolved as a package — the only
+ * paths into it.
+ *
+ * Two things this buys, and one it does not.
+ *
+ * It makes the entry points resolve under `node16`/`nodenext`. Without a map, those modes do
+ * no directory-index lookup, so `styled-system/tokens` does not resolve at all and the
+ * artifact has to be spelled `styled-system/tokens/index.mjs` — a workaround
+ * `token-references.ts` still has to recognise because people write it. Declaring `./tokens`
+ * is what makes the ordinary spelling work.
+ *
+ * It states the boundary. `css/merge-css`, `css/utilities`, `tokens/tokens` and `helpers`
+ * exist to be imported by the modules beside them, not by an app; a relative import inside
+ * the package is unaffected by this map, an external one now fails.
+ *
+ * What it does not do is enforce that against the common setup. The generated directory
+ * usually lives in the project and is reached through a `paths` alias —
+ * `"styled-system/*": ["./styled-system/*"]` — and a `paths` mapping resolves straight to the
+ * filesystem, so no `exports` map is consulted. There is nothing this file can do about that;
+ * the enforcement lands where the output is consumed as a real package, which is the
+ * component-library layout `emit-pkg` produces.
+ *
+ * `./types` carries no runtime target because the directory holds only declarations. A type
+ * import resolves; a value import fails, which is the truth about it.
+ */
+declare function generatePackageExports(ctx: Context, base?: string): Record<string, unknown>;
+//#endregion
+export { Generator, SplitCssArtifact, SplitCssResult, generatePackageExports, getThemeCss };