Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: error out if
npm
is used (#2736)
This PR introduces the usage of `please-use-pnpm` to cause usage of `npm` or `yarn` to bork e.g. ``` ❯ npm install npm warn EBADENGINE Unsupported engine { npm warn EBADENGINE package: '[email protected]', npm warn EBADENGINE required: { npm warn EBADENGINE npm: 'please-use-pnpm', npm warn EBADENGINE yarn: 'please-use-pnpm', npm warn EBADENGINE pnpm: '>=9.9.0', npm warn EBADENGINE node: '>=22.7.0' npm warn EBADENGINE }, npm warn EBADENGINE current: { node: 'v22.8.0', npm: '10.8.2' } npm warn EBADENGINE } npm error code 127 npm error path /path/to/ftl/node_modules/.pnpm/@codemirror[email protected]/node_modules/@codemirror/state npm error command failed npm error command sh -c cm-buildhelper src/index.ts npm error sh: cm-buildhelper: command not found npm error A complete log of this run can be found in: /path/to/ftl/.hermit/node/cache/_logs/2024-09-19T17_43_47_183Z-debug-0.log ``` > [!IMPORTANT] > there is another [blessed way](https://pnpm.io/only-allow-pnpm) to do this but i couldn't get it to work due to some `codemirror` linter thing that's caked in somewhere > [!IMPORTANT] > the example output above was produced by running `npm install` from within the `console` directory. presumably we'll want this to work from the root. @wesbillman i've got some questions for you before pushing that through
- Loading branch information