forked from logseq/logseq
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.npmrc
More file actions
20 lines (19 loc) · 933 Bytes
/
Copy path.npmrc
File metadata and controls
20 lines (19 loc) · 933 Bytes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
# Keep transitive npm packages reachable from the root node_modules so
# shadow-cljs browser builds can resolve them during compile and watch.
shamefully-hoist=true
# Prefer reusing the existing lockfile on regular installs.
# pnpm will try a frozen install first and may fall back to updating the lockfile
# if package.json changes are not reflected in pnpm-lock.yaml.
#
# This helps prevent:
# - unnecessary lockfile churn during routine local installs
# - dependency drift between developers or CI environments
# - non-reproducible builds across Windows / Linux / macOS
#
# CI should still use `pnpm install --frozen-lockfile` when a strict failure is required.
# To intentionally refresh dependencies or regenerate the lockfile, run:
# pnpm install --no-frozen-lockfile
#
# Recommended for local developer installs in team projects; pair it with
# `--frozen-lockfile` in CI for strict enforcement.
prefer-frozen-lockfile=true