-
Notifications
You must be signed in to change notification settings - Fork 100
-
Notifications
You must be signed in to change notification settings - Fork 100
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
New react-native deps breaks packager #77
Comments
Sounds similar to issue #66 . try reinstalling watchman? |
I am having the same problem currently. After many hours of debugging I still don't have a solution :( How to reproduce: re-natal init FutureApp
cd future-app
npm install
lein prod-build
react-native bundle --entry-file index.android.js --platform android --bundle-output android/app/src/main/assets/index.android.bundle The result is always
What I have tried:
Used operating systems:
Do you have any idea what the problem may be? |
I'm hitting this issue as well, with a fresh project, trying to run in my iOS simulator. Commands (copied from the README verbatim -- I've also tried starting the packager manually, with no change in behavior): npm install -g re-natal
re-natal init client -i reagent6
cd client
react-native run-ios Output:
|
I found the solution. Just downgrade babel plugin |
That works for me, too; thanks, @mizinin. What's the long-term fix for this, @drapanjanas et al? |
@jeaye Not too much I can think of actually. Generate project with hardocded version in package.json - not perfect as this can cause incompatibilities in future RN versions. But if no better ideas we could do that. |
Thanks! |
For what it's worth, the downgrade workaround no longer works. There is a bug on react-native regarding slow bundling on large javascript files: facebook/react-native#12590 (comment) |
Packager hangs on transforming in fresh created app.
It's not a re-natal problem, but maybe someone faced that problem and know the solution.
The text was updated successfully, but these errors were encountered: