We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey, I had an issue on Chrome 56.x when I got: Uncaught TypeError: $export is not a function console message on upon running the server first time.
Uncaught TypeError: $export is not a function
My issue seems to be solved by finding this post on stack. And changing transform-runtime to following:
transform-runtime
plugins: [ 'add-module-exports', 'transform-decorators-legacy', 'transform-class-properties', 'transform-object-rest-spread', ['transform-runtime', {helpers: false, polyfill: false, regenerator: true}] ]
The text was updated successfully, but these errors were encountered:
@alkavan seems like duplication of #5. Will try to fix it tomorrow. You may make a PR to make it faster
Sorry, something went wrong.
Merge pull request #7 from alkavan/master
e65d321
Issue #6 Adding option to 'transform-runtime' plugin to avoid getting…
fixed, we can close?
exclude: /(node_modules|bower_components)/,
fixed for me. Entire thing:
module: { rules: [ { test: /\.js$/, enforce: 'pre', loader: 'eslint-loader', query: { configFile: './.eslintrc' } }, { test: /\.js$/, exclude: /(node_modules|bower_components)/, use: [ { loader: 'babel-loader', options: { babelrc: true } } ] } ] },
No branches or pull requests
Hey, I had an issue on Chrome 56.x when I got:
Uncaught TypeError: $export is not a function
console message on upon running the server first time.My issue seems to be solved by finding this post on stack. And changing
transform-runtime
to following:The text was updated successfully, but these errors were encountered: