rsnext/.npmrc

provenance = true
save-exact = true
tag-version-prefix=""
strict-peer-dependencies = false
auto-install-peers = true
lockfile = true
fix: npm publish provenance permissions (#48757) Co-authored-by: Jiachi Liu <inbox@huozhi.im> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> 2023-04-24 16:08:55 +02:00			`provenance = true`
Pinned dependencies 2017-02-16 23:53:39 +01:00			`save-exact = true`
Remove version prefix 2018-10-02 01:35:56 +02:00			`tag-version-prefix=""`
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com> 2022-05-29 06:35:16 +02:00			`strict-peer-dependencies = false`
			`auto-install-peers = true`
declare pnpm7 as engine (#37303) Ensure to use npm v7, otherwise the lockfile will be messed with previous versions Related: https://pnpm.io/npmrc#lockfile 2022-05-30 15:13:36 +02:00			`lockfile = true`