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

Error when running packager #5190

Closed
dentrite opened this issue Jan 7, 2016 · 3 comments
Closed

Error when running packager #5190

dentrite opened this issue Jan 7, 2016 · 3 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@dentrite
Copy link

dentrite commented Jan 7, 2016

The message I got in chrome

TransformError: E:\\TestProject\\node_modules\\react-native\\node_modules\\react-transform-hmr\\node_modules\\react-proxy\\node_modules\\react-deep-force-update\\lib\\index.js: Cannot read property 'error' of null

react-native-cli@0.1.7, node.js 4.1 on Win 8

@facebook-github-bot
Copy link
Contributor

Hey dentrite, thanks for reporting this issue!

React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.

  • If you don't know how to do something or something is not working as you expect but not sure it's a bug, please ask on StackOverflow with the tag react-native or for more real time interactions, ask on Discord in the #react-native channel.
  • If this is a feature request or a bug that you would like to be fixed, please report it on Product Pains. It has a ranking feature that lets us focus on the most important issues the community is experiencing.
  • We welcome clear issues and PRs that are ready for in-depth discussion. Please provide screenshots where appropriate and always mention the version of React Native you're using. Thank you for your contributions!

@corbt
Copy link
Contributor

corbt commented Jan 7, 2016

Did this error just start after the upgrade to react-native 0.18-rc? It may be related to #5188, you have the same error message we've been running into. It looks like packager may not be passing through underlying babel error messages.

@corbt
Copy link
Contributor

corbt commented Jan 19, 2016

This should have been cleared up in 0.18. If it's still an issue after upgrading please reopen.

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

4 participants