===== Troubleshooting ===== ==== npm error code EBADENGINE ==== === Description === Using npm fails with the error "error code EBADENGINE" error code EBADENGINE error engine Unsupported engine error engine Not compatible with your version of node/npm: example@1.2.3 error notsup Not compatible with your version of node/npm: example@1.2.3 error notsup Required: {"node":">=16"} error notsup Actual: {"npm":"8.19.2","node":"v12.19.0"} === Reason === Your node engine is lower than the required one (12<16) === Fix === Install the required engine (16 or higher) nvm install 16 nvm use 16 Source [[https://stackoverflow.com/questions/70269056/cause-of-npm-warn-ebadengine|Stackoverflow.com - Cause of npm WARN EBADENGINE]] ==== fsevents not accessible ==== === Description === Using npm fails with the error "fsevents not accessible" or "failed optional dependency /example-master/node_modules/fsevents" === Reason === The dependency of this module should be optional === Fix === Make fsevents optional npm i fsevents@latest -f --save-optional Source [[https://stackoverflow.com/questions/68021121/fsevents-not-accessible-from-jest-haste-map|Stackoverflow.com - fsevents not accessible]] ==== webpack is missing ==== === Description === Using npm fails because webpack is missing === Reason === Webpack is missing === Fix === Install webpack npm install -S webpack Source [[https://stackoverflow.com/questions/38788166/webpack-command-not-working|Stackoverflow.com - webpack command not found]]