@uniweb/templates 0.1.1 → 0.1.2
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
|
@@ -134,7 +134,7 @@ Binary files (images, fonts, etc.) are copied as-is.
|
|
|
134
134
|
|
|
135
135
|
### Critical: Package Dependencies
|
|
136
136
|
|
|
137
|
-
**The site package MUST include the foundation as a
|
|
137
|
+
**The site package MUST include the foundation as a local dependency:**
|
|
138
138
|
|
|
139
139
|
```json
|
|
140
140
|
// site/package.json.hbs
|
|
@@ -142,16 +142,18 @@ Binary files (images, fonts, etc.) are copied as-is.
|
|
|
142
142
|
"name": "site",
|
|
143
143
|
"dependencies": {
|
|
144
144
|
"@uniweb/runtime": "^0.1.0",
|
|
145
|
-
"foundation": "
|
|
145
|
+
"foundation": "file:../foundation"
|
|
146
146
|
}
|
|
147
147
|
}
|
|
148
148
|
```
|
|
149
149
|
|
|
150
|
-
This `"foundation": "
|
|
151
|
-
1. pnpm
|
|
150
|
+
This `"foundation": "file:../foundation"` entry is essential because:
|
|
151
|
+
1. Both npm and pnpm create a symlink at `site/node_modules/foundation` pointing to the sibling foundation
|
|
152
152
|
2. Vite's `#foundation` alias resolves to the `foundation` module
|
|
153
153
|
3. Without this, the site build will fail with "Could not load foundation"
|
|
154
154
|
|
|
155
|
+
**Important:** Use `file:` protocol, not `workspace:*`. The `workspace:*` protocol is pnpm-specific and will fail with npm.
|
|
156
|
+
|
|
155
157
|
**Use fixed package names:**
|
|
156
158
|
- Foundation: `"name": "foundation"` (not `{{projectName}}-foundation`)
|
|
157
159
|
- Site: `"name": "site"` (not `{{projectName}}-site`)
|
package/package.json
CHANGED