source-maps

Does Chrome support multiple modules/sourceMappingURLs on a single javascript url

谁说我不能喝 提交于 2019-12-10 10:05:42
问题 I have been trying out the Source Maps feature in Chrome and have found that it does not support having a single javascript resource attached to a script tag that contains multiple modules concatenated together along with a //@sourceMappingURL comment separating each one . The first mapping is hooked up and I see the modules source associated in the debugger but all the others are ignored. I would expect that it would be a comment requirement to do this when multiple modules are minified and

Gulp Typescript + Browserify; Bundled sourcemap points to transpiled JS rather than source TS

冷暖自知 提交于 2019-12-10 06:36:27
问题 I'm working on a Typescript project that is transpiled to ES5 JS and then run through browserify to create a single .js bundle and sourcemap. The bundled sourcemaps point to the transpiled JS rather than the source TS even though I am generating sourcemaps which properly point to the source TS when transpiling to JS. It's as if browserify is ignoring the existing sourcemaps pointing to the TS code and creating its own new maps to the transpiled JS code. Here are my gulp tasks for reference-

Ionic 2 doesn’t generate scss source maps. “main.css.map” contains “null”

岁酱吖の 提交于 2019-12-10 04:24:58
问题 Could you help me to understand why Ionic 2 doesn't generate scss source maps. After "ionic serve" I'm navigating to www/build folder, there is main.css.map but it contains null instead of generated sourcemaps, how to fix it? Anyone faced this problem? 回答1: You'll need to extend your sass.config.js file, by default source mapping for sass is disabled. config/sass.config.js: module.exports = { sourceMap: true, } package.json: "config": { "ionic_sass": "./config/sass.config.js", }, https:/

Webpack 4 devtool option does not work with webpack-dev-server

僤鯓⒐⒋嵵緔 提交于 2019-12-10 02:56:34
问题 Before I decided to post this issue, I did quite a few things as a background check. So, my problem is: - I use webpack v4.6.0 and webpack-dev-server v3.1.3 - they work fine together, but now I am trying to set up source maps for my application, it seems that devtool option does not work. At least for me, I have tried and tested every option from the list: Webpack 4 - Sourcemaps : this issue suggests that devtool: 'source-map' should work out of the box, but this is not the case for me how to

Source Mapping in Coffeescript - errors not mapped to source

孤街浪徒 提交于 2019-12-10 01:54:56
问题 I just became aware of source mapping - a long awaited feature. I am impressed so many people got together to make it happen for coffee-script (browsers, kickstart project etc...) I set up a little test, so I could understand how to use it... Coffeescript N.B. there is a deliberate mistake here, as y is not defined console.log 123 sq = (x)-> x * x console.log "thats how easy: "+sq y Source Map { "version": 3, "file": "test.js", "sourceRoot": "", "sources": [ "test.coffee" ], "names": [],

Chrome Extension: Not loading source-maps

╄→гoц情女王★ 提交于 2019-12-09 13:01:59
问题 I am not able to load sourcemap in Chrome Extension for some reason. The folder which is being loaded for Chrome Extension has .map just next to .js file. With the .js file having the line //# sourceMappingURL=1.9215106f1980d05d2b4c.js.map referencing the .map file path. However, the Chrome dev-tools is not loading the maps for some reason. I double checked the Chrome settings to make sure that the js source maps is turned on and it is working with a simple Angular project. Also, made sure I

Problems generating source map files with current Gulp setup

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-08 04:40:29
I have set up a gulpfile.js in my project. It's working pretty nicely mostly, except when it comes to generating source maps, especially for the LESS files it compiles to CSS . I have put together a gist which contains all the files in my gulp setup. Please note that other than the gulp file.js itself, all the other files are inside a directory called tasks . The problems I am having are that I had to disable the autoprefixer in development because the source maps that were being generated were invalid as the autoprefixer modified the original CSS file after the source maps were generated. To

Debugging minified JavaScript in Visual Studio with sourcemaps

狂风中的少年 提交于 2019-12-08 04:00:08
问题 We have an ASP.NET 3.5 (IIS Application Pool 2.0) webSite. We are developing it with Visual Studio 2013 update4 in Windows8.1 . The problem is that: When I minify JavaScript files (with Web Essentials extension) and change the aspx files to use the newly created min.js files, the debugger of Visual Studio or any other browser wont works correctly. We expected that we work on the original js file (put a breakpoint etc. . .), and web browser runs it's minified min.js file (since relations exist

Problems generating source map files with current Gulp setup

可紊 提交于 2019-12-08 03:28:06
问题 I have set up a gulpfile.js in my project. It's working pretty nicely mostly, except when it comes to generating source maps, especially for the LESS files it compiles to CSS . I have put together a gist which contains all the files in my gulp setup. Please note that other than the gulp file.js itself, all the other files are inside a directory called tasks . The problems I am having are that I had to disable the autoprefixer in development because the source maps that were being generated

Cannot use Chrome Live Edit with Webpack source maps

北城以北 提交于 2019-12-08 01:49:16
问题 I have a webpack 4 configuration that generates source maps for my app's JavaScript. While debugging my app in Chrome, the source maps get loaded so I can see my unimified code. I'll set a breakpoint in a function and in the Sources tab I'll make edits to the code. I hit CMD+S to save my edits. Normally, I would expect Chrome to think for a little bit while it processes my edits and then I can continue debugging my session with my code changes. But that doesn't happen. I get a little yellow