@bleedingdev/modern-js-create 3.2.0-ultramodern.21 → 3.2.0-ultramodern.23

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.
package/README.md CHANGED
@@ -29,16 +29,17 @@ npx @modern-js/create my-app --router tanstack
29
29
 
30
30
  ### Tailwind Template
31
31
 
32
- You can scaffold Tailwind CSS v4 setup (PostCSS + starter utility classes):
32
+ Tailwind CSS v4 setup is generated by default. Disable it explicitly when you
33
+ need a plain CSS starter:
33
34
 
34
35
  ```bash
35
- npx @modern-js/create my-app --tailwind
36
+ npx @modern-js/create my-app --no-tailwind
36
37
  ```
37
38
 
38
- You can combine both options:
39
+ TanStack Router and Tailwind CSS work together without extra flags:
39
40
 
40
41
  ```bash
41
- npx @modern-js/create my-app --router tanstack --tailwind
42
+ npx @modern-js/create my-app --router tanstack
42
43
  ```
43
44
 
44
45
  ### BFF Runtime Template
@@ -65,24 +66,24 @@ Generated starters expose `presetUltramodern(...)` as the public opinionated
65
66
  config wrapper when you want the full Ultramodern setup surface in
66
67
  `modern.config.ts`.
67
68
 
68
- You can combine TanStack Router + Tailwind + Effect BFF in one command:
69
+ You can combine TanStack Router + default Tailwind + Effect BFF in one command:
69
70
 
70
71
  ```bash
71
- npx @modern-js/create my-app --router tanstack --tailwind --bff-runtime effect
72
+ npx @modern-js/create my-app --router tanstack --bff-runtime effect
72
73
  ```
73
74
 
74
75
  ### Micro Vertical Workspace Recipes
75
76
 
76
- Use the existing create flags to scaffold packages inside a Micro Vertical
77
- workspace. The shell and remotes use TanStack Router; services use Effect by
78
- default, with Hono kept as an explicit compatibility lane.
77
+ Use the workspace add flow from the UltraModern workspace root. It derives the
78
+ package path, package name, port, Module Federation name, topology entry, local
79
+ overlay, ownership entry, and root `dev:*` script from the requested name and
80
+ kind.
79
81
 
80
82
  ```bash
81
- npx @modern-js/create apps/shell --router tanstack --tailwind --workspace --sub
82
- npx @modern-js/create apps/remotes/catalog --router tanstack --tailwind --workspace --sub
83
- npx @modern-js/create apps/remotes/design-system --router tanstack --tailwind --workspace --sub
84
- npx @modern-js/create services/catalog-api --bff-runtime effect --workspace --sub
85
- npx @modern-js/create services/legacy-api --bff-runtime hono --workspace --sub
83
+ npx @modern-js/create catalog --microvertical remote
84
+ npx @modern-js/create design-system --microvertical horizontal-remote
85
+ npx @modern-js/create catalog-api --microvertical service
86
+ npx @modern-js/create catalog-contracts --microvertical shared
86
87
  ```
87
88
 
88
89
  When a design system needs independent deployment, treat it as a horizontal
@@ -92,6 +93,11 @@ regular workspace packages for tokens, primitives, generated clients, or
92
93
  domain-neutral utilities. Keep feature composites and workflow logic owned by a
93
94
  shell, remote, or service package.
94
95
 
96
+ The lower-level `--router`, `--workspace`, and `--sub` flags remain available
97
+ for manual package scaffolding, but UltraModern MicroVertical additions should
98
+ prefer `--microvertical` to avoid hand-writing workspace paths and topology
99
+ metadata.
100
+
95
101
  See
96
102
  `docs/super-app-rfc-adr/WORKSPACE-0001-micro-vertical-workspace-scaffolding.md`
97
103
  for the canonical workspace topology and local orchestration model.