Cheng Liu

For now, the workaround maybe creating a new file called `typings.d.ts` under your project, add the following content to this file. ``` declare namespace Chai { interface Assertion { toMatchSnapshot():...

> @chengcyber Is this the expected behavior? One guess is running "rush update --full" or "rush update --recheck" is needed after any modification of "pnpm-config.json". Kind of similar as running...

Updates 2022/8/7: 1. rebase latest main branch 2. rename pushRebuildArgs to pushPnpmRebuildCommandArgs 3. add a comment on Stage 1 4. throw error when specifying --ignore-scripts in non-pnpm repos 5. refactor...

As per zkochan said in this comment https://github.com/pnpm/pnpm/issues/4080#issuecomment-991651063, these three properties are ok in monorepo scenario. > `rush.json` or a separate file? I am not sure, but currently `rush.json` has...

Hi @octogonz , could you kindly take a look at this. I believe it helps a lot to fix tons of `peer deps` warnings in our monorepo.

Hi @octogonz , i saw your issue at https://github.com/pnpm/pnpm/issues/4407. And zkochan adds more pnpm.xxx configurations into pnpm. - `peerDependencyRules ` https://github.com/pnpm/pnpm/pull/4212 - `onlyBuiltDependencies` https://github.com/pnpm/pnpm/pull/4014 I'd like to add these fields...

> Can we just put these options in a separate file, whose schema is not tracked by Rush (so that new options added to pnpm don't require updates to Rush...

Update 2022/8/7: 1. rebase the main branch 2. Rush.js don't validate "pnpm.overrides", "pnpm.packageExtensions"... fields. Making the type to be unknown and leave pnpm to do the rest of work.

No worries @iclanton, i think this kind of "back and forth" shows me how Rush maintainers think of a "small feature" which may affect the whole system. I recalled in...

Hi @elliot-nelson, Thanks to your feedback! I tested the feature in this repo https://github.com/chengcyber/rush-pnpm-patch-demo, and it works. Could you reproduce the issue in this repo. It aims to patch "[email protected]"...