-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Problems debugging javascript #1480
Comments
That's a negative Ghost Rider. You want to be running what goes into production on dev. I do not cross my fingers and hope it works when I deploy to staging and production.
Yeah let's only enable |
Yeah, I think that's best. Is there a way to do the same for |
Well I guess you want it to stay in JSHint so you know the debug statement should be removed at some point right? JShint should only fail the build if it's |
Yeah so JSHint was failing the task always. Now it only fails the build when you run scripts through |
While working with a Sage project,
gulp; gulp watch
uglify
is stripping out anydebugger;
statements (not to mentionjshint
complains about it too).I can add
"debug": true
to.jshintrc
but that obviously isn't great for production use.It seems we need to be able to pass some different options to
jshint
anduglify
if we're not runninggulp --production
. Perhaps foregouglify
at all if not production?The text was updated successfully, but these errors were encountered: