Firefox has lots of room to improve if it wants to beat Chrome

Re:Firefox has lots of room to improve if it wants to beat C... by Isinlor on Sunday September 01, 2019 @08:02AM (#20851817)

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

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-...

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...

[ Parent | on HN ]

Re:Firefox has lots of room to improve if it wants to beat C... by sroussey on Sunday September 01, 2019 @01:12PM (#20853365)

Source maps don’t work well on Chrome either. :/

[ Parent | on HN ]

Re:Firefox has lots of room to improve if it wants to beat C... by JMTQp8lwXL on Sunday September 01, 2019 @03:10PM (#20854108)

Your 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).

[ Parent | on HN ]