Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

268
Views
How to fix my app after 'npm audit fix --force'

For some context, I am a web developer by day, but in the evenings, I work on a personal project using React Native, and I'm still fairly new to it. The app was working totally fine up until a couple of days ago, and I'm not entirely what caused it. Even if I revert back in GitHub, things still do not work.

Things that I think have caused it are:

  • Running 'npm audit fix --force'

  • Or updating node, npm, or expo-cli

What I've tried so far:

  • I've gone back to a previous commit where the app was definitely working, tried to start the app ('expo start'), but to no avail

  • I've made sure the package.json, package-lock.json, and yarn.lock were all reverted, and then ran 'npm install', and the yarn equivalent (I'm aware you shouldn't mix package managers but this has been like it even when the app was working, so fairly sure this isn't the issue)

  • Un-ignored node_modules/ in .gitignore, then deleted them from the project, and ran 'npm install', and yarn equivalent

  • Tried clearing all caches (npm, metro etc.)

  • 'expo doctor --fix dependencies'

  • Tried reverting expo-cli to a previous version, same with npm and node

  • Debugged the app with remote debugger in Chrome which I'll explain below...

Symptoms of the issue:

  • It seems to be at build time (I think?) because the app never makes it to any kind of components or screens:Error in iOS simulator when I try to serve my app using 'expo start' and 'i'

r/reactnative - how can I fix my app after 'npm audit fix --force' Error in iOS simulator when I try to serve my app using 'expo start' and 'i'

  • The message I'm getting is 'no stack', because of a "}" symbol (pics will be included), and when I trace this down to its root using the remote debugging in chrome, the caught exception that it paused on was something like 'can't use import statement outside of a module', and the line seems to be referring to Babel module:Using Expo remote debugger in Chrome

r/reactnative - how can I fix my app after 'npm audit fix --force' Using Expo remote debugger in Chrome

  • When I try to serve the app on web, I get a different Webpack related error (please see screenshots)

I won't put my package.json etc. here because it'll be a wall of text, but here's my repo if anyone would like to see the dev dependencies etc.: https://github.com/braingame-com/bg1

This has caused me so much frustration that I considered just rebuilding the app from scratch because it's not very far along anyway, but I'm really wanting to get my debugging skills up and learn what I had done wrong, rather than taking the easy way out.

What can I try next?

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!