FluidFramework/.npmrc

engine-strict=true

# Temporary, because otherwise pnpm fails due to peer dependencies not being satisfied
# with our current dependency graph.
strict-peer-dependencies=false
build: Require at least node >=14.13.0 and npm ^6 (#12922) Reviving #10847. Enforce that the version of node used is at least 14.13.0 (released on 2020-09-29), which according to https://www.the-guild.dev/blog/support-nodejs-esm means it should support ESM. This uses the mechanism documented in https://docs.npmjs.com/cli/v8/configuring-npm/package-json#engines. This produces an error when running `npm i` in the root if using an older version of node. Note that the 14 branch of node is the oldest supported branch (see https://nodejs.org/en/about/releases/), no one should be one node older than 14, so updating to at least 14.13.0 should be a non-breaking change. Additionally, our `.nvmrc` file specifies node 14, and our readme says to use that version. Since this is in the root package.json, not one we ship to users, it should have no impact on consumers of our packages. ## Example Error If I force requiring version 15 instead (so my system errors) the error looks like: ``` $ npm i npm ERR! code ENOTSUP npm ERR! notsup Unsupported engine for root@0.14.0: wanted: {"node":">=15.13.0"} (current: {"node":"14.19.3","npm":"6.14.17"}) npm ERR! notsup Not compatible with your version of node/npm: root@0.14.0 npm ERR! notsup Not compatible with your version of node/npm: root@0.14.0 npm ERR! notsup Required: {"node":">=15.13.0"} npm ERR! notsup Actual: {"npm":"6.14.17","node":"14.19.3"} ``` I have confirmed `npm ci` also produces this error. 2022-11-15 05:53:56 +03:00			`engine-strict=true`
build(client): Use pnpm in client release group (#13554) This PR changes the client release group to use pnpm instead of npm. lerna now uses the pnpm workspace config and uses pnpm to execute scripts. ## Things that should still work Note: `fluid-build` === `npm run build:fast` - fluid-build should continue to build the repo incrementally. - `fluid-build --install` should use pnpm for the release groups that use it and npm elsewhere. - You can still use npm to run scripts, e.g. `npm run build`, or you can switch to pnpm e.g. `pnpm build`. Co-authored-by: Rishhi Balakrishnan <107130183+RishhiB@users.noreply.github.com> 2023-01-26 01:36:03 +03:00
			`# Temporary, because otherwise pnpm fails due to peer dependencies not being satisfied`
			`# with our current dependency graph.`
			`strict-peer-dependencies=false`