source-maps

grunt-contrib-less: compilation on watch task removes sourcemap link

醉酒当歌 提交于 2019-12-12 01:39:53
问题 Here's my less task config: less: { development: { options: { compress: false, sourceMap: true, yuicompress: true, sourceMapFilename: 'export/style/app.css.map', sourceMapURL: '/style/app.css.map' }, files: { "export/style/app.css": "less/app.less" } } }, If I just type grunt less , in my compiled file i get the /*# sourceMappingURL=/style/app.css.map */ comment correctly. Instead, when i run grunt and my watch task kicks in, the /*# sourceMappingURL=/style/app.css.map */ comment is removed

webpack 4.2 – how can I obtain the original source file name and line line number, where the error was thrown?

≡放荡痞女 提交于 2019-12-11 13:25:20
问题 By default Webpack 4 is using UglifyJS for minifying the code. In the production I am getting an unusable error message point to the column of the compiled javascript file. The documentation https://webpack.js.org/guides/migrating/#uglifyjsplugin-sourcemap claims that one should be able to obtain the correct line by setting sourceMap to true in the UglifyJS Plugin. I've tried it, but that's not working. Here's the respective webpack config file: const webpack = require('webpack'); const

Is there a way to show the Ruby line numbers in javascript generated by Opal

我的未来我决定 提交于 2019-12-11 12:34:07
问题 For debugging purposes I would like to see the corresponding Ruby Source position in the javascript file generated by Opal. Is there a simple way to achive this? I tried # config.ru require 'bundler' Bundler.require run Opal::Server.new { |s| s.append_path 'public' s.append_path 'src' s.debug = true s.source_map = true s.main = 'application' s.index_path = 'index_opal.html' } this is my application file require 'math' require 'opal' require 'opal-jquery' require 'consolelogger' require

webstorm 7/karma server looking for wrong sourcemap file when debugging coffeescript

旧巷老猫 提交于 2019-12-11 11:21:16
问题 I am having a devil of a time trying to get the debugger to work with my coffeescript files when testing with the karma test runner. Supposedly, all I need to do is tell the Webstorm file watcher to generate sourcemaps and the debugger will work with the karma test runner. Unfortunately, the debugger doesn't seem to recognize the map file output by the coffeescript compiler. It looks for file.coffee -> file.js.map. However, despite trying to get some other result the map file is always file

vscode react-native typescript breakpoint not hit: source map

亡梦爱人 提交于 2019-12-11 11:18:49
问题 I have been struggling with this problem for more that one year. I have filed an issue here. I have tried to apply the solution description there and from countless suggestions all over internet (example). Here is my configuration node v8.9.1 npm 4.6.1 react-native-cli 2.0.1 react-native 0.54.2 vscode 1.21.1 Here is my tsconfig.json: { "compilerOptions": { "target": "es2015", "module": "es2015", "jsx": "react-native", "moduleResolution": "node", "allowSyntheticDefaultImports": true,

How do I provide source-level debugging for a language like VS does for TypeScript?

允我心安 提交于 2019-12-11 11:17:46
问题 I understand the concept of using source maps with JavaScript to make debugging easier with minified scripts, etc. What I don't get is how source-level debugging works like it does for TypeScript in Visual Studio (http://blogs.msdn.com/b/typescript/archive/2012/11/15/announcing-typescript-0-8-1.aspx). For example, if I create my own language that compiles/translates to JavaScript, how do I interface with browsers to provide this kind of source-level debugging? Is there a standard protocol for

Debug Typescript in Chrome bundled by Webpack Visual Studio 2017 .NET Core 2.2

限于喜欢 提交于 2019-12-11 07:45:47
问题 There are a couple questions out there but most of the answers seem to be "it should be default now if you have VS 2017". My debugger isn't working, so I'd like to give my specific case to get some help. I'm also new to Typescript & Webpack to give some context. Project Hiearchy ./wwwroot/bundles/bundle.js <- this is the final bundled file ./Scripts/ <- various directories where all the separate Typescript files live When the project builds, it goes through these steps: Core project builds

WebStorm 7 - Yeoman Angular missing sourcemaps `Failed to load resource: the server responded with a status of 404 (Not Found)`

孤街浪徒 提交于 2019-12-11 05:46:24
问题 Running the yeoman angular generator grunt server with WebStorm 7.0.1 throws: Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/bower_components/jquery/jquery.js.map:0 Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/bower_components/angular/angular.js.map:0 Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/bower_components/bootstrap-sass/js

How to configure sourceMaps for LESS using Grunt when there is more than one file in your project?

强颜欢笑 提交于 2019-12-10 21:32:13
问题 I have multiple .less files that I want processed to their matching .css with sourceMaps for each file all in the same folder as the source. How hard can that be? I have no problem in doing this directly with less but cant figure out how to do this in grunt-contrib-less as it seems to want the sourceMapFilename to be a single hard coded value. This my gruntfile: module.exports = function(grunt) { grunt.initConfig({ pkg: grunt.file.readJSON("package.json"), watch: { options: { livereload: true

How can I specify a file source map after the page loads up?

一个人想着一个人 提交于 2019-12-10 13:19:44
问题 I'm a big fan of source maps for javascript and SASS; however, I don't want to load source maps into production for a couple of reasons: the original source code is available and it's not a good use of bandwidth. But, sometimes, the need for debugging in production arises (we've all seen production-only bugs on the front-end). Is there a way for me to specify a source map after the fact? For example, I could have a source map available locally or behind a VPN-locked server, or even in a