what's the difference using eval and eval-source-map?

Question

I am using webpack to config the source map. I am wondering anyone could clarify the difference between "eval" and "eval-source-map" ? I don't see the difference personally.

P Ackerman · Accepted Answer · 2018-07-07 14:19:33Z

10

From the documentation:

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.

Essentially eval-source-map is slower, but has more accurate mapping to the original line numbers (helpful for identifying the appropriate lines of bugs in the original source code).

answered Jul 7, 2018 at 14:19

P Ackerman

2,43423 silver badges25 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

lynnic Over a year ago

why eval-source-map has fater rebuild speed?

Collectives™ on Stack Overflow

what's the difference using eval and eval-source-map?

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related