source-maps

How do you guys do maintenance on CSS built with Less/Sass? One of the things I like about Dev Tools/Firebug is the ability to see the line number of a css styling. Is there a good way to do this with CSS preprocessors other than having to manually search through the .less/.scss file to find the code I want to modify? Chrome Developer Tools now supports Sass debugging out-of-the-box. Updated to include source maps: Previous versions used inline comment in your css to provide a refernce to the source code (see below how-to). recent versions of sass (3.3+) and chrome (31+) use source maps for

Should source-maps be used in production environment? Do they provide any benefits other than debugging? Do they impact app load time due to the additional server round-trips? Are browsers smart enough to load .map assets after app is loaded and rendered? If a browser cannot find the .map asset ( 404 error), would there be performance impact? Should I care about fixing it? Note that fixing the last one may not be as easy as serving the .map assets if there are complicated concat / minify build steps. A quick test using Charles Web Proxy shows that source maps are only loaded if developer tools

I'm trying to write a gulp task allowing me to use modules in JS (CommonJS is fine), using browserify + 6to5. I also want source mapping to work. So: 1. I write modules using ES6 syntax. 2. 6to5 transpiles these modules into CommonJS (or other) syntax. 3. Browserify bundles the modules. 4. Source maps refers back to the original ES6 files. How to write such a task? Edit: Here's what I have so far: gulp task gulp.task('browserify', function() { var source = require('vinyl-source-stream'); var browserify = require('browserify'); var to5ify = require('6to5ify'); browserify({ debug: true })

When I'm loading the minified (through UglifyJS) version of my AngularJS application, I get the following error in the console: Unknown provider: aProvider <- a Now, I realize that this is due to variable name mangling. The unmangled version works just fine. However, I do want to make use of variable name mangling, as it drastically reduces the size of our JS output file. For that reason, we're using ngmin in our build process, but it doesn't seem to resolve this issue, even though it served us well in the past. So, to debug this issue, I enabled source maps in our uglify grunt task. They are

I received error log like the following while the app crashed: Fatal Exception: com.facebook.react.modules.core.JavascriptException: onSelect index.android.bundle:20:7148 onPress index.android.bundle:20:2435 But it's not really helpful for me to trouble shoot. How could I enable source map so that I could track down where the issue is ? UPDATE 2018 https://docs.expo.io/versions/latest/guides/using-sentry.html Looks promising ! For source mapping here is the way I go about it: In my bundle command for my production build I tell it to generate a source map: iOS: react-native bundle --platform