carboncanvas 0.1.0

package/vite.d.ts

@@ -0,0 +1,33 @@
+// Types for the `carboncanvas/vite` subpath (the carbonPreset helper). Hand-
+// authored (not generated by vite-plugin-dts): the preset is a build-time Node
+// module that re-exports the data-anchor babel plugin, so it lives OUTSIDE the
+// React library's dts-rollup surface (which only covers the runtime canvas API).
+
+export interface CarbonPresetOptions {
+  /**
+   * Reserved. Durable source-anchored pins need `dataAnchorBabelPlugin` wired
+   * into your react() plugin's `babel.plugins` (a config fragment can't reach
+   * into it), so this flag is documentation/forward-compat only.
+   */
+  dataAnchor?: boolean;
+}
+
+/** The Vite config fragment carbonPreset returns. */
+export interface CarbonViteFragment {
+  esbuild: { keepNames: true };
+}
+
+/**
+ * The Carbon Canvas Vite config fragment — spread into your `vite.config` to
+ * preserve component names in the production build (`esbuild.keepNames`).
+ */
+export declare function carbonPreset(opts?: CarbonPresetOptions): CarbonViteFragment;
+
+/**
+ * The data-anchor Babel plugin, re-exported so you can pass it to your own
+ * `react({ babel: { plugins: [dataAnchorBabelPlugin] } })` for durable pins.
+ */
+// eslint-disable-next-line @typescript-eslint/no-explicit-any
+export declare const dataAnchorBabelPlugin: (babel: any) => any;
+
+export default carbonPreset;

package/vite.js

@@ -0,0 +1,42 @@
+// carbonPreset — a Vite config fragment for Carbon Canvas consumers
+// (plan §6.2 / amendment B.5). Spread it into your `vite.config` so the
+// production build preserves component names the Inspector reads off the live
+// fibers:
+//
+//   import { carbonPreset } from 'carboncanvas/vite';
+//   export default defineConfig({ ...carbonPreset(), plugins: [react()] });
+//
+// WHY A FRAGMENT + A SEPARATE PLUGIN RE-EXPORT (not one all-in-one preset):
+// the fragment can safely set esbuild.keepNames, but the OPTIONAL data-anchor
+// babel plugin has to live inside @vitejs/plugin-react's `babel.plugins` option
+// — which a top-level config fragment cannot reach into without knowing your
+// react() call. So the plugin is RE-EXPORTED here (`dataAnchorBabelPlugin`) and
+// you pass it to your own react() plugin, matching the documented pattern:
+//
+//   import { carbonPreset, dataAnchorBabelPlugin } from 'carboncanvas/vite';
+//   export default defineConfig({
+//     ...carbonPreset(),
+//     plugins: [react({ babel: { plugins: [dataAnchorBabelPlugin] } })],
+//   });
+
+import dataAnchorBabelPlugin from './tools/babel-plugin-data-anchor.js';
+
+/**
+ * Returns the Carbon Canvas Vite config fragment. Today that is
+ * `{ esbuild: { keepNames: true } }` — the one setting that keeps the Inspector
+ * showing REAL component names in a minified production build.
+ *
+ * @param {{ dataAnchor?: boolean }} [opts] Reserved. Durable source-anchored
+ *   pins need the `dataAnchorBabelPlugin` re-export wired into YOUR react()
+ *   plugin's babel option (a config fragment can't reach into it) — see the
+ *   module header. The flag is accepted for forward-compat and documentation.
+ */
+export function carbonPreset(opts = {}) {
+  void opts;
+  return {
+    esbuild: { keepNames: true },
+  };
+}
+
+export { dataAnchorBabelPlugin };
+export default carbonPreset;