Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Starter fails with missing module #3

Open
joelpresence opened this issue Nov 14, 2017 · 6 comments
Open

Starter fails with missing module #3

joelpresence opened this issue Nov 14, 2017 · 6 comments

Comments

@joelpresence
Copy link

I followed your steps:

git clone https://github.com/HandlebarLabs/currency-converter-starter.git
cd currency-converter-starter
git checkout module-3-lesson-1
npm install

When I do npm start I get:

Unable to resolve module `react-native/Libraries/Renderer/shims/ReactNativeBridgeEventPlugin` from `/Users/joel/src/react-native/currency-converter-starter/node_modules/react-native-gesture-handler/GestureHandler.js`: Module does not exist in the module map

This might be related to https://github.com/facebook/react-native/issues/4968
To resolve try the following:
  1. Clear watchman watches: `watchman watch-del-all`.
  2. Delete the `node_modules` folder: `rm -rf node_modules && npm install`.
  3. Reset packager cache: `rm -fr $TMPDIR/react-*` or `npm start -- --reset-cache`.

ABI19_0_0RCTFBQuickPerformanceLoggerConfigureHooks
ABI19_0_0RCTFBQuickPerformanceLoggerConfigureHooks
ABI19_0_0RCTFBQuickPerformanceLoggerConfigureHooks





CFRunLoopRunSpecific
GSEventRunModal
UIApplicationMain
Exponent

I tried all the cleans etc and nothing worked. The only thing that worked is npm install --save react-native-gesture-handler@1.0.0-alpha.29.

See also facebook/react-native#4968

Any ideas?

Thanks! :-)

@spencercarli
Copy link
Contributor

Thanks for reporting! I'm going to try and take a look at this tomorrow

@joelpresence
Copy link
Author

joelpresence commented Nov 14, 2017 via email

@spencercarli
Copy link
Contributor

Should be fixed now! Give it a shot and let me know

@joelpresence
Copy link
Author

joelpresence commented Nov 17, 2017 via email

@smooJitter
Copy link

@spencercarli why was this happening?

@spencercarli
Copy link
Contributor

@smooJitter no idea. I just upgraded the packages around the time (4564256) and haven't seen or heard of this issue since.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants