-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[core] regeneratorRuntime is not defined #1182
Comments
same issue here, just try to set up vue-material in my plain new project but this annoy me, no way to figure out. |
Looks like its because you doesnt have await/async: https://stackoverflow.com/a/33527883 |
@Samuell1 - Thanks! This actually was the solution... That is now my package.json: my .babelrc: and on the top of my index.js i added: |
This is quite strange. I will take a deep look. The babel stuff should be built in Vue Material. |
Maybe the transform-async-to-generator transform could be an alternative to using babel-polyfill: |
yes, but babel-polyfill adds support for all things not only 1 @marsvin |
Whats the status of this issue? Shouldnt Vue Material work without external polyfills? or else the getting started has to be updated? |
I get the same error in my typescript+webpack project when importing individual components:
But not when importing the whole module:
and using the exact same template with just some simple layout components. |
Same issue here:
Any chance to get the PR merged soon? |
Hi, I'm new to Vue, just tried to follow the 'getting started' documentation and got this error. Which I see is closed. How do you fix it please? |
@RichardJECooke After PR will be merged it should work like is written in docs, now you need to use
|
That would be awesome @FrancescoMussi ; import a whole css file when you only use some components doesn't make too much sense... |
Agreed @FrancescoMussi @ZiFFeL1992 , that would be incredibly useful, especially for older projects migrating to vuematerial. |
In my case I need to import full VueMaterial. Importing single componetns generates this error |
This issue should be fixed in dev branch. |
@Samuell1 is it available already as npm package? |
No, its only in dev branch @michjk |
@Samuell1 Any update on this? When will it be released? |
The same for me, importing components throws a "regeneratorRuntime is not defined" error, but importing full VueMaterial is ok. |
I'm having the same issue as @asmi77 |
@jordigoyanes @highco issue is solved in DEV branch like i said in comments before, we waiting to release new version from @marcosmoura that will fix this issue. |
New release is out and this should be fixed with it! If you anything find feel free to ping me here :) https://github.com/vuematerial/vue-material/releases/tag/v1.0.0-beta-10 |
I poorly just don't get this to run.
Steps to reproduce
As soon as I import -
import { MdApp } from 'vue-material/dist/components'
import 'vue-material/dist/vue-material.min.css'
Vue.use(MdApp)
to my project, I get:
index.js:1 Uncaught ReferenceError: regeneratorRuntime is not defined at index.js:1 at Object../node_modules/vue-material/dist/components/index.js.Object.defineProperty.value (index.js:1)
I am working with JeffreyWay/laravel-mix
let mix = require('laravel-mix'); mix.js('resources/assets/spa/main.js','public/js/app')
Happens also if i try to import the whole bundle or other components.
The text was updated successfully, but these errors were encountered: