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.

Sign up for GitHub

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

Jump to bottom

Uncaught SyntaxError: Unexpected token } #1551

Closed
2 of 10 tasks
joachimvdnab opened this issue May 2, 2018 · 1 comment
Closed
2 of 10 tasks

Uncaught SyntaxError: Unexpected token } #1551

joachimvdnab opened this issue May 2, 2018 · 1 comment

Comments

@joachimvdnab
Copy link

joachimvdnab commented May 2, 2018 •
edited
Loading

Issue details

This issue was fixed in 2.23.6, but is reintroduced in version 2.24.1 by re-adding sourcemaps for the client.

9e900df

Steps to reproduce/test case

Please provide necessary steps for reproduction of this issue, or better the
reduced test case (without any external dependencies).

Please specify which version of Browsersync, node and npm you're running

  • Browsersync [ 2.24.1 ]
  • Node [ 6.4.0 ]
  • Npm [ 3.10.3 ]

Affected platforms

  • linux
  • windows
  • OS X
  • freebsd
  • solaris
  • other (please specify which)

Browsersync use-case

  • API
  • Gulp
  • Grunt
  • CLI
@shakyShane
Copy link
Contributor

Ooops! fixed in browser-sync@2.24.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shakyShane @joachimvdnab