# Temporary: nunjucks@3.2.4 declares an optional peer on chokidar@^3.3.0.
# This repo uses chokidar@5 directly for hot reload, while jsonUtils keeps
# Nunjucks file watching disabled (`watch: false`), so npm install needs the
# peer conflict relaxed until the upstream constraint is removed or nunjucks is replaced.
legacy-peer-deps=true

# npm 12 changed the `allow-remote` default to `none`, which refuses every non-registry
# dependency before fetching it. `@minipuft/repository-standards-validation` is a pinned
# tarball (https://github.com/minipuft/repository-standards/archive/refs/tags/vX.Y.Z.tar.gz),
# so `root` permits exactly the remote specs written in this project's own package.json.
# Without it, `npm install` under npm 12 fails with EALLOWREMOTE, which is how Renovate's
# lockfile-maintenance artifact step on server/package-lock.json fails. npm 11 does not know
# the key and prints `Unknown project config "allow-remote"` on every run.
allow-remote=root
