Files
angular__angular/integration/cli-hello-world/pnpm-workspace.yaml
T
Alan Agius e90423f5f7 build: disable strict release age checks in pnpm workspaces
Updates all pnpm-workspace.yaml configurations across the repository to set minimumReleaseAgeStrict: false. This resolves dependency installation failures caused by missing time field metadata in the npm registry for certain packages such as @babel/helper-globals. A TODO comment is also added to each configuration file to track future investigation of this registry metadata issue.
2026-05-12 10:43:00 -07:00

23 lines
847 B
YAML

allowBuilds:
'@parcel/watcher': false
esbuild: false
lmdb: false
msgpackr-extract: false
# The minimum age of a release to be considered for dependency installation.
# The value is in minutes (1440 minutes = 1 day).
minimumReleaseAge: 1440
# List of packages to exclude from the minimum release age check.
minimumReleaseAgeExclude:
- '@angular-devkit/*'
- '@angular/*'
- '@ngtools/webpack'
- '@schematics/*'
- 'ng-packagr'
- 'zone.js'
# TODO: Investigate why without minimumReleaseAgeStrict: false it fails with such errors:
# [ERR_PNPM_MISSING_TIME] The metadata of @babel/helper-globals is missing the "time" field
# This error happened while installing the dependencies of @angular-devkit/build-angular@22.0.0-next.7
# at @babel/preset-env@7.29.2
# at @babel/plugin-transform-classes@7.28.6
minimumReleaseAgeStrict: false