Closed iamkevinlowe closed 8 years ago
Running npm install
a second time installs babel-runtime
and the build succeeds when starting the simulator, but now I'm getting Uncaught Error: Uncaught ReferenceError: require is not defined
in Chrome's dev tools console.
So I was getting the babel-runtime error this morning before I merged the CircleCI updates. I actually got the same error on a unrelated branch.
My ultimate solution was to restart my computer. I believe it has something to do with babel-runtime not being found because because a node process is still running.
Before restarting run ps aux | grep node
to see if node is still running without the simulator of the react node server is running.
I did this:
rm -rf node_modules
npm install
I'm still getting the same error. When I run npm ls --depth=0
I'm getting this:
├── babel-core@6.7.4
├── babel-eslint@6.0.2
├── babel-plugin-transform-runtime@6.6.0
├── babel-polyfill@6.7.4
├── babel-preset-react-native@1.5.6
├── babel-runtime@6.6.1
├── chai@3.5.0
├── enzyme@2.2.0
├── eslint@2.7.0
├── eslint-config-airbnb@6.2.0
├── eslint-plugin-import@1.4.0
├── eslint-plugin-react@4.2.3
├── eslint-plugin-react-native@1.0.0
├── estraverse-fb@1.3.1
├── lodash@4.8.2
├── moment@2.12.0
├── react@0.14.8
├── react-addons-test-utils@0.14.8
├── react-dom@0.14.8
├── react-native@0.20.0
├── react-native-mock@0.0.6
└── react-native-simple-store@0.1.0
npm ERR! missing: babel-runtime@^5.0.0, required by babel-code-frame@6.7.4
npm ERR! missing: babel-runtime@^5.0.0, required by babel-generator@6.7.2
npm ERR! missing: babel-runtime@^5.0.0, required by babel-helpers@6.6.0
npm ERR! missing: babel-runtime@^5.0.0, required by babel-messages@6.7.2
npm ERR! missing: babel-runtime@^5.0.0, required by babel-template@6.7.0
npm ERR! missing: babel-runtime@^5.0.0, required by babel-traverse@6.7.4
npm ERR! missing: babel-runtime@^5.0.0, required by babel-types@6.7.2
npm ERR! missing: babel-runtime@^5.0.0, required by babylon@6.7.0
(more npm errors removed for brevity)
Trying to run the simulator here returns the babel-runtime error above. Running npm install
again, seems like it installs the babel-runtime
dependencies, and npm ls --depth=0
doesn't show the npm errors. The simulator now opens, but still getting the Uncaught ReferenceError
.
Totally lost 😩
Let's pair on this. The errors aren't making sense.
Getting this error when running simulator. Reinstalling modules:
rm -rf node_modules && npm install
gives the same error.