Installing @bugsnag /expo with npm. This could take a while!

Error: spawn npm ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

When I went through the course, I didn’t install bugsnag. But, the ENOENT error from npm is saying that there’s no such file or directory open.

Maybe check this out: Using Bugsnag - Expo Documentation

And, verify that you have the correct version of npx installed.

hello @abdul ,

Try to update your npm to the latest version: npm install -g npm@latest
(mine is v7.6.0)

and try to install @bugsnag /expo again
npm install @bugsnag /expo

Hello,
When the app is running, sometimes it caused me some errors during new package installation process.
So, before I do further research, I stop the app (Ctrl+c in VS code terminal as we know) and then retry it first.
Hope this works for you too.
Have a good one!

For this error, I managed to solve it by first update the npm by typing this command “npm install -g npm@latest” on the terminal. After doing so, try to install bugsnag without installing it globally, instead install it only on the project directory by typing “npm install bugsnag-expo-cli”. Lastly try to run this command “bugsnag-expo-cli init” but it will prompt the user to install the bugsnag, for this just press “n” for no, and it will ask the user to give the bugsnag API key.

After doing so, if you can’t import from “ @bugsnag /expo” just use npm to install it by using “npm install @bugsnag /expo”, and it should works fine.