create-claude-workspace 1.1.95 → 1.1.96

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.
@@ -340,13 +340,14 @@ The path MUST point to the **library root directory** (where `package.json` live
340
340
  // package.json (root or consuming app)
341
341
  {
342
342
  "dependencies": {
343
- "theme": "workspace:./libs/ui/theme" // pnpm/bun
344
- // or "file:./libs/ui/theme" for npm
345
- // If repo has a scope: "@[scope]/theme": "workspace:./libs/ui/theme"
343
+ "theme": "workspace:./libs/ui/theme"
344
+ // With scope: "@[scope]/theme": "workspace:./libs/ui/theme"
346
345
  }
347
346
  }
348
347
  ```
349
348
 
349
+ **ALWAYS use `workspace:` protocol** — NEVER use `file:` (it creates a copy instead of a symlink, breaking live updates). `workspace:` works in bun, pnpm, and npm 7+.
350
+
350
351
  **NEVER point to a subdirectory** like `./libs/ui/theme/src/generated/theme` or `./libs/ui/theme/src` — always the library root with `package.json`. The `exports` field in that `package.json` handles the mapping.
351
352
 
352
353
  Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use '@[scope]/theme/colors'` with scope) resolves automatically.
@@ -230,13 +230,14 @@ The path MUST point to the **library root directory** (where `package.json` live
230
230
  // package.json (root or consuming app)
231
231
  {
232
232
  "dependencies": {
233
- "theme": "workspace:./libs/ui/theme" // pnpm/bun
234
- // or "file:./libs/ui/theme" for npm
235
- // If repo has a scope: "@[scope]/theme": "workspace:./libs/ui/theme"
233
+ "theme": "workspace:./libs/ui/theme"
234
+ // With scope: "@[scope]/theme": "workspace:./libs/ui/theme"
236
235
  }
237
236
  }
238
237
  ```
239
238
 
239
+ **ALWAYS use `workspace:` protocol** — NEVER use `file:` (it creates a copy instead of a symlink, breaking live updates). `workspace:` works in bun, pnpm, and npm 7+.
240
+
240
241
  **NEVER point to a subdirectory** like `./libs/ui/theme/src/generated/theme` or `./libs/ui/theme/src` — always the library root with `package.json`. The `exports` field in that `package.json` handles the mapping.
241
242
 
242
243
  Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use '@[scope]/theme/colors'` with scope) resolves automatically.
@@ -230,13 +230,14 @@ The path MUST point to the **library root directory** (where `package.json` live
230
230
  // package.json (root or consuming app)
231
231
  {
232
232
  "dependencies": {
233
- "theme": "workspace:./libs/ui/theme" // pnpm/bun
234
- // or "file:./libs/ui/theme" for npm
235
- // If repo has a scope: "@[scope]/theme": "workspace:./libs/ui/theme"
233
+ "theme": "workspace:./libs/ui/theme"
234
+ // With scope: "@[scope]/theme": "workspace:./libs/ui/theme"
236
235
  }
237
236
  }
238
237
  ```
239
238
 
239
+ **ALWAYS use `workspace:` protocol** — NEVER use `file:` (it creates a copy instead of a symlink, breaking live updates). `workspace:` works in bun, pnpm, and npm 7+.
240
+
240
241
  **NEVER point to a subdirectory** like `./libs/ui/theme/src/generated/theme` or `./libs/ui/theme/src` — always the library root with `package.json`. The `exports` field in that `package.json` handles the mapping.
241
242
 
242
243
  Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use '@[scope]/theme/colors'` with scope) resolves automatically.
@@ -258,13 +258,14 @@ The path MUST point to the **library root directory** (where `package.json` live
258
258
  // package.json (root or consuming app)
259
259
  {
260
260
  "dependencies": {
261
- "theme": "workspace:./libs/ui/theme" // pnpm/bun
262
- // or "file:./libs/ui/theme" for npm
263
- // If repo has a scope: "@[scope]/theme": "workspace:./libs/ui/theme"
261
+ "theme": "workspace:./libs/ui/theme"
262
+ // With scope: "@[scope]/theme": "workspace:./libs/ui/theme"
264
263
  }
265
264
  }
266
265
  ```
267
266
 
267
+ **ALWAYS use `workspace:` protocol** — NEVER use `file:` (it creates a copy instead of a symlink, breaking live updates). `workspace:` works in bun, pnpm, and npm 7+.
268
+
268
269
  **NEVER point to a subdirectory** like `./libs/ui/theme/src/generated/theme` or `./libs/ui/theme/src` — always the library root with `package.json`. The `exports` field in that `package.json` handles the mapping.
269
270
 
270
271
  Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use '@[scope]/theme/colors'` with scope) resolves automatically.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-claude-workspace",
3
- "version": "1.1.95",
3
+ "version": "1.1.96",
4
4
  "description": "Scaffold a project with Claude Code agents for autonomous AI-driven development",
5
5
  "type": "module",
6
6
  "bin": {