source-maps

Visual Studio Debugging with Source Maps

由 随声附和 提交于 2019-12-07 20:08:17
问题 I am using Microsoft Visual Studio 2013 Update 4 to debug a web application. First, I ran the web application on Internet Explorer and then I attach the iexplore script process using the Debug option "Attach to process" in Visual Studio. Then I immediately get a new node in the Solution Explorer called 'Script Documents'. In that node, I find all of the JavaScript files along with their respective typescript files listed. From then on, I am able to open the JavaScript files and set

VS Code sourceMapPathOverrides

由 ＊爱你＆永不变心＊ 提交于 2019-12-07 10:29:19
问题 I have an Aurelia TypeScript project where my compiled JavaScript files go into the .../wwwroot subfolder and the original typescript files are located in .../src . I am trying to use the Chrome Debugger extension in VS code but breakpoints are not hit and when I turn on diagnosticLogging in launch.json the the mapped source is incorrect: It look in .../wwwroot/src/file.ts instead of .../src/file.ts . I tried to solve this with sourceMapPathOverrides but with no success. It seems I cannot

Webpack source maps pointing to minified bundle

由 十年热恋 提交于 2019-12-07 08:00:34
问题 I'm setting up a Webpack build process for an existing project and have been running into some issues with source maps. I am using devtool: 'eval-source-map', . If an error happens in the browser, every file / line number in the stack trace points to a file condensed into a single line in the Webpack bundle. For example, a first line of a stack trace might look like this: Uncaught Error: foo at child.initialize (eval at (http://127.0.0.1:8000/js/dist/index.js:1270:1), :45:10) Clicking on the

How to configure angular-cli to create inline sourcemaps?

由 你。 提交于 2019-12-07 03:38:53
问题 angular.json only gives the option to turn on/off sourcemap generation but by default it's in separate files. tsconfig.json gives also the inlineSources option but it's ignored by angular-cli. Is there a way to tell angular-cli to write the source maps inside the .js? 回答1: To whom it may concern, here is the approach I implemented to enable debugging with source maps support on Android devices install ngx-build-plus by running npx ng add ngx-build-plus This will install the required npm

chrome 72 changes sourcemap behaviour

由 僤鯓⒐⒋嵵緔 提交于 2019-12-07 02:49:03
问题 I'm developing a Webextension for Chrome, the code is written in Typescript, so I need sourcemaps. The extension is bundled with ParcelJS, but I believe that my problem is not related to the bundler. After updating from Chrome 70 to 72, sourcemaps no longer work. As a minimal example, I can reproduce the problem on MacOS 14 and Ubuntu 18.04, Chrome 72 with the following code. This problem seems to be isolated to Chrome 72. Unfortunately, at the time of writing, that's the current stable

How to set a breakpoint at a lambda call in Google Chrome DevTools?

由 随声附和 提交于 2019-12-06 19:04:53
问题 I use Babel and Google Chrome Developer Tools with JavaScript source maps enabled. Given this code function myFunc(elements) { return elements .map(element => element.value) .filter(value => value >= 0); } how can I pause execution at execution of lambda function element => element.value ? If I set a breakpoint at line of .map(element => element.value) it will only pause when map is executed, but not when the lambda function is executed. 回答1: This feature is finally available (at least in

Cannot use Chrome Live Edit with Webpack source maps

由 |▌冷眼眸甩不掉的悲伤 提交于 2019-12-06 14:30:20
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 icon next to my file in the Sources tab that says "Changes to this file were not saved to the filesystem

Path to source map is wrong

由 情到浓时终转凉″ 提交于 2019-12-06 08:35:23
问题 I use the packages gulp-less and gulp-sourcemaps . My less file is located under Styles/main.less , but the generated source map points to source/main.less (where source/ seems to be a prefix). How to fix this, so the source map correctly points to source/Styles/main.less ? My gulp task is rather simple: var gulp = require('gulp'), less = require('gulp-less'), gulpif = require('gulp-if'), sourcemaps = require('gulp-sourcemaps'); var paths = { styles: [ 'Styles/**/*.less', '!**/*.min.css' ],

Webpack with sourcemap can't resolve variables in production mode

由 ∥☆過路亽．° 提交于 2019-12-06 06:34:50
问题 I would like to generate source maps for our production build with Webpack. I managed to generate it, but when I stop on a breakpoint in the debugger, variables are not resolved: What am I doing wrong? How can I generate a source map that lets the chrome devtools resolve the variables once I stopped on a breakpoint in the debugger? These are my webpack configurations: webpack.config.js : const path = require('path'); const ROOT = path.resolve( __dirname, 'src/main/resources/packedbundle' );

Gulp SASS Sourcemap sources are incorrect

由 我的梦境 提交于 2019-12-06 05:07:41
问题 I am struggling to get my SASS sourcemaps to work correctly. The problem seems to be the "sources" attribute within the sourcemap and how my SASS files are nested. I have a Gulp task that compiles SASS to CSS. Here is an example of that var paths = { styles: { src: './Stylesheets/SCSS/', files: './Stylesheets/SCSS/**/*.scss', dest: './Stylesheets/CSS/' } } gulp.task('compile-sass', function (){ return gulp.src(paths.styles.files) .pipe(sourcemaps.init()) .pipe(sass({ outputStyle: 'compressed'
订阅 source-maps