3 ms·
I use Firefox all the time and use it for web development. But modern frontend stack - with the whole pile of transpilers, uglifiers, and what not - is almost
by Isinlor 7y ago
I use Firefox all the time and use it for web development.
But modern frontend stack - with the whole pile of transpilers, uglifiers, and what not - is almost unusable with Firefox, because source maps don't work with Webpack.
https://github.com/webpack/webpack/issues/1194 https://github.com/webpack/webpack/issues/1194
This put me in a position where I had to choose between switching to Chrome for development or not using Webpack that comes nicely integrated into the web framework of my choice.
I went with ditching Webpack, but it's hard.
https://stackoverflow.com/questions/55669725/require-module-without-webpack-etc https://stackoverflow.com/questions/55669725/require-module-...
Developers will not use Firefox if FF dev tools are inferior to Chrome.
Some comments from devs:
> Can we please fix this? I don't want to choose Chrome as the browser only coz of this issue.
Mozzila took notice of the issue after 4 years...
- sroussey 7y agoSource maps don’t work well on Chrome either. :/
- JMTQp8lwXL 7y agoYour linked issue says that certain types of source maps will work with Firefox. Can't you just use one of the working options (e.g, "eval-source-map" works but "cheap-source-map" does not).