Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`regeneratorRuntime` is not defined

See original GitHub issue

This is a:

Bug Report

Which concerns:

flow-runtime

What is the current behaviour?

flow-runtime.min.js:3 Uncaught (in promise) ReferenceError: regeneratorRuntime is not defined
    at eval (flow-runtime.min.js:3)
    at eval (flow-runtime.min.js:3)

What is the expected behaviour?

Throw error

Please add babel-plugin-transform-runtime is your .babelrc

Which package versions are you using?

0.2.1

Issue Analytics

State:
Created 7 years ago
Reactions:3
Comments:12 (1 by maintainers)

Top GitHub Comments

4reactions

reaperescommented, Jan 22, 2017

In my case, I add a line of code in webpack.dev.config file. Please comments if it’s not correct.

entry: {
  app: [
    'regenerator-runtime/runtime',
    'webpack-hot-middleware/client',
    './app/index.js'
  ]
},

2reactions

ForbesLindesaycommented, Apr 29, 2017

The correct solution to this is to add https://babeljs.io/docs/plugins/transform-runtime/ to the babel config for flow-runtime. You do not need to worry about this causing a duplicate version of the regenerator runtime to exist, because flow-runtime should not be used in production anyway, and the regenerator-runtime added by babel-plugin-transform-runtime does not pollute the global scope, so it won’t conflict with any applications that use regenerator themselves. Without this, libraries that use flow-runtime will not work out of the box.

I’m going to be forced to abandon flow-runtime until this is fixed.