You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks again for maintaining this awesome project @wellyshen.
I'd like to know your opinion on changing the eval source mapping to eval-source-map. Just to refresh you this is from the webpack docs:
eval - Each module is executed with eval() and //@ sourceURL. This is pretty fast. The main disadvantage is that it doesn't display line numbers correctly since it gets mapped to transpiled code instead of the original code (No Source Maps from Loaders).
eval-source-map - Each module is executed with eval() and a SourceMap is added as a DataUrl to the eval(). Initially it is slow, but it provides fast rebuild speed and yields real files. Line numbers are correctly mapped since it gets mapped to the original code. It yields the best quality SourceMaps for development.
It seems like eval can be slightly confusing as the line numbers are not displayed correctly. I've been using eval-source-map on a big project and it seems fast and more suited to easier development.
The text was updated successfully, but these errors were encountered:
Thanks again for maintaining this awesome project @wellyshen.
I'd like to know your opinion on changing the
eval
source mapping toeval-source-map
. Just to refresh you this is from the webpack docs:eval
- Each module is executed witheval()
and//@ sourceURL
. This is pretty fast. The main disadvantage is that it doesn't display line numbers correctly since it gets mapped to transpiled code instead of the original code (No Source Maps from Loaders).eval-source-map
- Each module is executed witheval()
and a SourceMap is added as a DataUrl to theeval()
. Initially it is slow, but it provides fast rebuild speed and yields real files. Line numbers are correctly mapped since it gets mapped to the original code. It yields the best quality SourceMaps for development.It seems like eval can be slightly confusing as the line numbers are not displayed correctly. I've been using
eval-source-map
on a big project and it seems fast and more suited to easier development.The text was updated successfully, but these errors were encountered: