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

SyntaxError in (Vue.js + Krama + Webpack + PhantomJS) #47

Open
yenarue opened this issue Jul 3, 2018 · 3 comments
Open

SyntaxError in (Vue.js + Krama + Webpack + PhantomJS) #47

yenarue opened this issue Jul 3, 2018 · 3 comments

Comments

@yenarue
Copy link

yenarue commented Jul 3, 2018

Hello. I'm a beginner for Web Programming and Vue.js. 😃
so... Although I'm not sure that is a issue of vue-youtube-embed, I hope you can help me.

Yesterday, I committed my code and was resting. but I suddenly found a build error in CircleCI.
I checked the following error message from npm test.

  SyntaxError: Unexpected token 'const'
  at http://localhost:9877webpack:///node_modules/vue-youtube-embed/lib/vue-youtube-embed.js:13:0 <- index.js:113108

It was so weird. because it was not associated with my commit totally.
So, I tried rebuilding a previously successful build. But I found the same error message. 😢
It's the same in local environment. I've checked all of my babel, webpack, and es6, even re-created the project, but I got the same error.

It's frustrating that a successed build suddenly gets an error. and I am more embarrassed that there is no solution at all.

Is it an known issue? or am I missing something?

vue-youtube-embed version is...

"vue-youtube-embed": "^2.2.0",

If you need other infomations, ask me.

I wait your answer. :-)
Regards.

@kaorun343
Copy link
Owner

@yenarue

I changed not to convert ES2015 to ES5 since 2.2.0, and your issue caused by this breaking change......

However, vue-youtube-embed/dist/vue-youtube-embed.umd.js is transpiled to ES5, so could you use this instead...?

@kwasnicki
Copy link

I just ran into the same issue. Our pipeline broke on this change. Wondering if the 2.2.0 update should be a 3.x update since this seems it could be a breaking change for apps with a ^2.x.x dependency?

@kaorun343
Copy link
Owner

Ah, I found that my rollup's configuration was incorrect.
I'll publish v2.2.1 soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants