uniweb 0.8.16 → 0.8.18

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.
Files changed (2) hide show
  1. package/README.md +12 -15
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -261,41 +261,38 @@ _Foundation-first_ — You're building a component system. The site is a test ha
261
261
 
262
262
  ## Growing Your Project
263
263
 
264
+ > **Install the CLI globally** with `npm i -g uniweb` for the best experience. You can also use `npx uniweb` or `pnpm uniweb` without a global install.
265
+
264
266
  Start simple. Add what you need, when you need it:
265
267
 
266
268
  ```bash
267
- cd my-site
269
+ # Create a blank workspace
270
+ uniweb create my-workspace --blank
271
+
272
+ cd my-workspace
268
273
 
269
274
  # Add a co-located foundation + site pair
270
275
  uniweb add project blog
271
276
 
272
277
  # Add a second foundation at root
273
- uniweb add foundation ui
278
+ uniweb add foundation DocKit
274
279
 
275
280
  # Add a site wired to a specific foundation
276
- uniweb add site docs --foundation ui
281
+ uniweb add site docs --foundation DocKit
277
282
 
278
283
  # Add an extension (auto-wired to the only site)
279
284
  uniweb add extension effects
280
285
 
281
286
  # Scaffold + apply content from an official template
282
287
  uniweb add project marketing --from marketing
288
+
289
+ # Install dependencies and run in dev mode
290
+ pnpm install # or npm install
291
+ pnpm dev # or npm run dev
283
292
  ```
284
293
 
285
294
  The workspace grows organically. `add` handles placement, wires dependencies, updates workspace globs, and generates root scripts. The name you provide becomes both the directory name and the package name. Use `--path` to override default placement, or `--project` for explicit co-located layouts.
286
295
 
287
- > **Install the CLI globally** with `npm i -g uniweb` for the best experience. You can also use `npx uniweb` or `pnpm uniweb` without a global install.
288
-
289
- **Or start blank and build up:**
290
-
291
- ```bash
292
- pnpm create uniweb acme --blank
293
- cd acme
294
- uniweb add project main
295
- pnpm install
296
- pnpm dev
297
- ```
298
-
299
296
  ## The Bigger Picture
300
297
 
301
298
  The structure you start with scales without rewrites:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "uniweb",
3
- "version": "0.8.16",
3
+ "version": "0.8.18",
4
4
  "description": "Create structured Vite + React sites with content/code separation",
5
5
  "type": "module",
6
6
  "bin": {
@@ -41,14 +41,14 @@
41
41
  "js-yaml": "^4.1.0",
42
42
  "prompts": "^2.4.2",
43
43
  "tar": "^7.0.0",
44
- "@uniweb/runtime": "0.6.11",
45
- "@uniweb/core": "0.5.10",
46
- "@uniweb/kit": "0.7.11"
44
+ "@uniweb/core": "0.5.12",
45
+ "@uniweb/kit": "0.7.13",
46
+ "@uniweb/runtime": "0.6.13"
47
47
  },
48
48
  "peerDependencies": {
49
- "@uniweb/build": "0.8.15",
50
- "@uniweb/semantic-parser": "1.1.6",
51
- "@uniweb/content-reader": "1.1.4"
49
+ "@uniweb/build": "0.8.17",
50
+ "@uniweb/content-reader": "1.1.4",
51
+ "@uniweb/semantic-parser": "1.1.6"
52
52
  },
53
53
  "peerDependenciesMeta": {
54
54
  "@uniweb/build": {