docs(only-allow-pnpm): added option to enforce pnpm with package.json and .npmrc #691
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Hello team!
I propose a very non-invasive update to the documentation—a native solution to a bug that has spawned numerous issues on GitHub.
As described in this issue (and many more open and closed issues), the package
only-allowcannot reliably prevent NPM commands from running (even as a preinstall script).Therefore, I added an alternative—a native solution that simply specifies PNPM as
packageManagerinpackage.jsonand setsengine-strictastruein.npmrc. This prevents commands from anything other than what's specified as the package manager.I also documented the option to install only-allow as a dev dependency for offline and CI/CD use cases.
Thank you,
Karthik Appiah