-
Notifications
You must be signed in to change notification settings - Fork 44
error with sourcemaps #68
Comments
Could you try to provide a small repo with a file/module where this error occurs ? I'm currently debugging this and a failing example would be quite helpful :) |
Sure @michael-ciniawsky, this is the repository https://github.com/pyrite-components/pyrite-prism . You have to install as global nodemon and typescript. To reproduce the fail you need to execute |
In particular, I found |
Got the same problem, using |
Just want to chime in that this is happening to me too. Ref webpack/webpack#5931 For those unfamiliar with |
Running
|
Also having this problem with the 'source-map' option. |
Just wanted to chip in and say that in my case it doesn't matter if i use the Also wanted to provide you with my files used: Cases
|
I'm running into the same problem. I worked around it by pinning |
So what's going on here? It seems like a breaking commit has been identified and that, most of the time, |
I'd guess cheap-* "fixing" it is since IIRC that disables minification source mapping (not much point mapping line-by-line if you only output one line!), but that doesn't narrow it down much. Seems there are plenty of references to this, so probably plenty of repro cases, just needs someone to spend the time on it. |
I'm also facing this issue. |
Problem still exists? If yes please create minimum reproducible test repo. Thanks! |
I commented out BabiliPlugin and it was working.
|
@arbaaz Incredible solution |
I feel a bit bad about saying this, but I changed to Uglify-es and got very good results both wrt to compilation speed and sourcemaps. |
@tarjei i near future i implement |
@evilebottnawi |
Right now i will develop Btw in near future i will implement minimize function to support using |
It was required to work around a source map bug when using newer `webpack-sources` with `babel-minify-webpack-plugin`: webpack-contrib/babel-minify-webpack-plugin#68 However now that we're using `uglify-es` instead, we can stop pinning the `webpack-sources` version and pick up some of the bug/perf fixes: https://github.com/webpack/webpack-sources/releases
Any fix / workaround available for this issue ?
I did the same but it's a bit unfortunate ... |
Disable source-map for production due to issue with Babel plugin. See webpack-contrib/babel-minify-webpack-plugin#68
@jbelien - use uglify. thats what I'm doing. |
Fixes minification. webpack-contrib/babel-minify-webpack-plugin#68
Workaround to AfterShip#151 Due to webpack-contrib/babel-minify-webpack-plugin#68
Workaround to AfterShip#151 Due to webpack-contrib/babel-minify-webpack-plugin#68
source-map 관련 버전, 의존성 오류로 보임. webpack-contrib/babel-minify-webpack-plugin#68 gatsby에서 socurcemap을 비활성화하는 플러그인을 이용한 해결 gatsbyjs/gatsby#3817
A too large commit containing too many additions, most of which will be refactored. This commit lays the foundation for the calendar system, providing functionality to navigate months and highlighting dates. The additions can be summarized as follows: - Add component that keeps track of all calendar data and sub-components. Uses JavaScript's type. - Add module containing utility functions for interacting with JavaScript's type. - Add component that lays out a calendar month in a CSS grid. - Add file for localized theme settings. - Disable source maps in production due to Webpack errors. For similar issues, see webpack-contrib/babel-minify-webpack-plugin#68. - Other small things such as setting app-wide styles with , adding (Danish) names for months and weekdays, and adding scss support.
I reproduce this issue when I use source maps with this plugin.
My config file:
The error which I get is this:
When I use the source maps without this plugin it works fine.
The version plugin is: 0.2.0
The text was updated successfully, but these errors were encountered: