docs: le pair optionnel @ng-org/orm dit ce que pnpm fait vraiment
Les deux textes expliquaient que `bun install` ne va pas chercher le pair optionnel. Mesure : pnpm ne le va pas chercher non plus pour un consommateur qui ne le nomme pas (un paquet qui ne declare que le polyfill recoit zero @ng-org, sans avertissement) - mais ce depot-ci l-obtient quand meme, parce que `packages/polyfill` le declare aussi en devDependency. Un `pnpm install` depuis un `node_modules` vide suffit donc a faire construire le bundle du runner, et le message qui demandait d-installer l-ORM a la main etait devenu un faux conseil.
This commit is contained in:
@@ -156,8 +156,10 @@ async function main(): Promise<void> {
|
||||
} catch (e) {
|
||||
console.error(
|
||||
"[orm-live] the bundle did not build. `@ng-org/orm` is an OPTIONAL PEER of this " +
|
||||
"package and `bun install` does not fetch it — install it in packages/polyfill " +
|
||||
"before running this measurement. NOTHING was measured, so nothing is concluded.",
|
||||
"package, so an application that does not name it gets nothing - but THIS " +
|
||||
"checkout declares it in packages/polyfill devDependencies, and `pnpm install` " +
|
||||
"does fetch that. So the ORM is not missing by design here: run `pnpm install` " +
|
||||
"at the repository root. NOTHING was measured, so nothing is concluded.",
|
||||
);
|
||||
console.error(String((e as { stderr?: Buffer })?.stderr ?? e));
|
||||
process.exit(1);
|
||||
|
||||
Reference in New Issue
Block a user