-
Notifications
You must be signed in to change notification settings - Fork 751
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
Unexpected Token { in browser console on fresh new yeoman+fountainJS projects #1498
Comments
I got this error too and figured out that When other plugins concatenate to that script the first line of the plugin script get corrupted. For example, with But with (Also commented on the issue here: BrowserSync/browser-sync-client#45) |
My temporary workaround is to remove the line with In |
@johanberonius Thanks for investigating :) I will fix & release within a few hours. |
@johanberonius @theCrius please try [email protected] |
Will do first thing in the morning (UK here) Thanks for the quick fix :) |
Yes, it works. Thanks for the quick fix! |
@johanberonius thanks to you for finding the bug! |
Confirmed as well, it's fixed. Thanks to both of you! |
Issue details
I'm using Yeoman with FountainJS to generate a new project.
As soon as it finish assembling it, I simply run the classic
npm run serve
. It finishes without errors but then I get this error in chrome browser console:The error is reported to be generated from
browser-sync-client.js?v=2.23.5:89
.My doubt is if the issue is actually in browserSync or in something else built by fountainJS package.
I tried building an angularJS (simple landing page) and angular (todo mcv) project but the error persist with both cases even if they're different framework/languages/source.
Steps to reproduce/test case
npm run serve
Please specify which version of Browsersync, node and npm you're running
From
package,json
:Others:
Affected platforms
Browsersync use-case
for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync
From
gulpfile.js
:The text was updated successfully, but these errors were encountered: