-
Notifications
You must be signed in to change notification settings - Fork 25
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
Sourcemaps don't seem to work with Browsersync? #14
Comments
I have seen some issues inside Browsersync but when viewed outside Browsersync or manually refreshing Browsersync window, they do work. This might have something to do with how Browsersync takes only new changes and applies them to the browser insted of refreshing the whole thing. It might be a Gulp issue that is already fixed in newest Gulp. We are testing enhancements for our build tools (upgrading to newer Gulp or going to Webpack) and this issue might be fixed at then unless this is inevitable incompatibility between Browsersync and sourcemaps. |
Gulp and other packages are upgraded in 5.0.0. Can you check if you are still having this issue? |
I checked - the issue still remains. |
This is a known Chrome issue. Any luck with other browsers? |
Worth noting, I find that the source maps will show up in Chrome after manually refreshing the browser. |
@kauaicreative You are right. In Firefox, the sourcemaps work properly even with live reload. |
This might be a problem with my environment but I wanted to ask that does it work elsewhere?
The text was updated successfully, but these errors were encountered: