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

babelHelpers.asyncGenerator.wrap not defined #10798

Closed
arv opened this issue Nov 8, 2016 · 6 comments
Closed

babelHelpers.asyncGenerator.wrap not defined #10798

arv opened this issue Nov 8, 2016 · 6 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@arv
Copy link
Contributor

arv commented Nov 8, 2016

Description

When adding transform-async-generator-functions to .babelrc I'm getting an error:

undefined is not an object  (evaluating 'babelHelpers.asyncGenerator.wrap')

Reproduction

.babelrc:

{
  "presets": ["react-native"],
  "plugins": [
    "transform-async-generator-functions"
  ]
}

Js code:

async function* f() {}

According to #4844 this seems to be because RN changes how babelHelpers works?

Additional Information

  • React Native version: 0.36
  • Platform: both
  • Operating System: macOS
@ErikCupal
Copy link

The problem is still present.

  • RN version 0.39.2
  • transform-async-generator-functions version 6.17.0

@christopherdro
Copy link
Contributor

@ErikCupal Still having issues?

@santiagofm
Copy link
Contributor

santiagofm commented Jul 20, 2017

Could you solve this issue @arv @ErikCupal @christopherdro ?

@arv
Copy link
Contributor Author

arv commented Jul 20, 2017

I didn't. We ended up not using async generators after all.

@JulioC
Copy link

JulioC commented Jul 21, 2017

@santiagofm you can try the solution on #14933

In my case, using react-native 0.46.x, it was enough to just downgrade babel-preset-react-native to 2.0.0 and run react-native start --reset-cache

@pull-bot
Copy link

pull-bot commented Oct 9, 2017

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos hramos added the Icebox label Oct 9, 2017
@hramos hramos closed this as completed Oct 9, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Oct 9, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Oct 9, 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

8 participants