@token-forge/core 0.3.3 → 0.3.4-nightly-20260725040904

package/README.md

@@ -0,0 +1,59 @@
+# @token-forge/core
+
+Token Forge pipeline bundle — profile definition, the Terrazzo build pipeline, and re-exports of `@token-forge/lib`, `@token-forge/plugins`, and `@token-forge/token-schema` in one package.
+
+Most consumers won't import this directly — it's pulled in automatically by [`@token-forge/cli`](https://www.npmjs.com/package/@token-forge/cli). Use it when you want to build a custom `terrazzo.config.ts` or bootstrap a design-system profile from code.
+
+## Install
+
+```bash
+npm i @token-forge/core
+```
+
+## Usage
+
+A consumer's `design-system.config.ts` calls `defineDesignSystemProfile` (re-exported from `@token-forge/lib`):
+
+```ts
+import { defineDesignSystemProfile } from "@token-forge/core";
+
+export const designSystemProfile = defineDesignSystemProfile({
+  id: "acme",
+  designSystems: [{ id: "acme" }],
+  tokenLayers: ["quarks", "color", "fixed", "fluid"],
+  themes: { modifier: "theme", lightSuffix: "-light", darkSuffix: "-dark" },
+  outputs: { plugins: ["css-variables", "typography"] },
+  figma: { terrazzoRemap: "./remappers/acme.ts", sources: [/* … */] },
+});
+```
+
+A thin `terrazzo.config.ts` builds on top of the profile:
+
+```ts
+// @token-forge/core/terrazzo
+import { createTerrazzoPipeline } from "@token-forge/core/terrazzo";
+import { designSystemProfile, SYSTEM_IDS } from "./design-system.config";
+
+export const { configForSystem } = createTerrazzoPipeline({
+  profile: designSystemProfile,
+  systems: SYSTEM_IDS,
+  repoRoot: import.meta.dirname,
+});
+export default configForSystem(SYSTEM_IDS[0]);
+```
+
+## Exports
+
+| Entry point                   | What it provides                                                                              |
+| ----------------------------- | --------------------------------------------------------------------------------------------- |
+| `@token-forge/core`           | Profile schema, pipeline helpers, and everything from `lib`/`plugins`/`token-schema`          |
+| `@token-forge/core/bootstrap` | `bootstrapDesignSystem` — register a profile from code without a config file                  |
+| `@token-forge/core/terrazzo`  | `createTerrazzoPipeline` — builds `terrazzo.config.ts`'s `configForSystem`/`pluginsForSystem` |
+
+## Docs
+
+Full setup guide: [Adopting `@token-forge/core`](https://github.com/blabassi/token-forge/blob/main/docs/adopting-core.md).
+
+## License
+
+MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@token-forge/core",
-  "version": "0.3.3",
+  "version": "0.3.4-nightly-20260725040904",
   "description": "Token Forge pipeline bundle — profile, Terrazzo plugins, token schema, Figma import",
   "license": "MIT",
   "author": "Badi Labassi",
@@ -24,10 +24,10 @@
   "dependencies": {
     "@terrazzo/cli": "^2.2.0",
     "@terrazzo/plugin-css": "^2.2.0",
-    "@token-forge/lib": "0.3.3",
-    "@token-forge/plugins": "0.3.3",
-    "@token-forge/figma-importer": "0.3.3",
-    "@token-forge/token-schema": "0.3.3"
+    "@token-forge/lib": "0.3.4-nightly-20260725040904",
+    "@token-forge/plugins": "0.3.4-nightly-20260725040904",
+    "@token-forge/figma-importer": "0.3.4-nightly-20260725040904",
+    "@token-forge/token-schema": "0.3.4-nightly-20260725040904"
   },
   "devDependencies": {
     "@types/node": "^24.0.0",

package/src/terrazzo-pipeline.ts

@@ -92,8 +92,21 @@ export function resolveOutputPluginsSync(
   if (!entries.length) {
     throw new Error("profile.outputs.plugins must be a non-empty list");
   }
+  const seenRefsById = new Map<string, string>();
   const plugins = entries.map((entry) => {
     const id = isPathRef(entry.id) ? derivedIdFromPath(entry.id) : entry.id;
+    const previousRef = seenRefsById.get(id);
+    if (previousRef !== undefined && previousRef !== entry.id) {
+      // Two distinct plugin refs (e.g. "./plugins/foo.ts" and "./shared/foo.ts") derive the
+      // same registry id from their filename — they'll silently resolve to the same
+      // registered plugin instead of two different ones. Warn instead of running one plugin
+      // twice with no indication the other was never actually loaded.
+      console.warn(
+        `resolveOutputPluginsSync: "${entry.id}" and "${previousRef}" both derive plugin id "${id}" — ` +
+          `they will resolve to the same registered plugin. Rename one file to avoid this collision.`,
+      );
+    }
+    seenRefsById.set(id, entry.id);
     try {
       return { plugin: getBuildPlugin(id), options: entry.options };
     } catch {