A lockfile-compatibility fix plus documentation updates.
Lockfile compatibility
nub install failed with ERR_NUB_MANIFEST_PARSE ("invalid type: map, expected a string") on a valid pnpm-lock.yaml when a package's engines: field held a nested map instead of a string range. Some legacy packages (e.g. cordova-plugin-inappbrowser) put a nested cordovaDependencies map under engines, which pnpm preserves verbatim in the lockfile. Nub's lockfile parser now tolerates non-string engines values — keeping the string ranges and ignoring the nested extras — matching how it already parses package.json. (#439, fixes #417)
Documentation
| Area | What changed | Commit |
|---|---|---|
| Vite+ comparison | New "Nub vs Vite+" comparison guide | b5bae7f |
| Vite+ comparison | Table updated with per-tool attributions | 7dfbe01 |
| Vite+ comparison | Package-manager shims marked partial (npm only) | 6a310f0 |
| Vite+ comparison | Expanded prose on runtime augmentation and scope | 6e31cf6 |
| Vite+ comparison | Runtime-augmentation feature list added | 8cfba4f |
| Bun-to-nub guide | Recommend DX-mirroring, trusted alternatives | 4478fbb |
| Docs sidebar | Separators render as visible rules | e384f8f |
What's Changed
- fix(lockfile): tolerate nested-map engines values in pnpm-lock.yaml by @colinhacks in #439
Full Changelog: v0.4.7...v0.4.8
Contributors
colinhacks