fix: corriger l'échec du build docker lié aux scripts de build ignorés par pnpm - #108
Merged
Conversation
iliesmrf
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issues liées
Aucune.
Quel est le comportement actuel ?
Le build de l'image docker échoue à l'étape
pnpm install:Le Dockerfile installe pnpm sans version fixée (
npm install --location=global pnpm),chaque build récupère donc la dernière version publiée. pnpm 10 bloque par défaut les
scripts de cycle de vie des dépendances et, contrairement à pnpm 9, sort en erreur au
lieu d'émettre un avertissement. Le script postinstall d'esbuild, qui télécharge son
binaire natif, est concerné. Le code et le lockfile n'ont pas changé, seule la version
de pnpm a bougé.
Quel est le nouveau comportement ?
package.json: ajout depnpm.onlyBuiltDependencies: ["esbuild"]pour autoriserexplicitement le script postinstall d'esbuild. Sans lui, le binaire natif est absent
et
pnpm run buildéchouerait à l'étape suivante.Dockerfile: pnpm est épinglé surpnpm@10pour que la version ne dérive plusd'un build à l'autre.
Vérifié en local :
docker build --target buildpasse,pnpm installpuisvitepress build docsse terminent sans erreur.Cette PR introduit-elle un breaking change ?
Non.
Autres informations
Aucune.