Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support merging sourcemaps when transformed file is fully replaced #14247

Merged
merged 2 commits into from Feb 8, 2022
Merged

Support merging sourcemaps when transformed file is fully replaced #14247

merged 2 commits into from Feb 8, 2022

Commits on Feb 7, 2022

  1. Support merging sourcemaps when transformed file is fully replaced 

    A follow-up to babel#14246. I finally thought of a case where the
sourceFileName's content is fully replaced, leading to only the injected
file existing in the output sourcemap. This can happen where only one
output source is created, or multiple.

In the single output source case, we'd incorrectly associate the
mappings through the inputMap, even though none of the content actually
comes from there.

In the multiple source case, we'd silently fail and output empty mappings.

Both cases are now fixed, with the correct remapping being done through
in all possible output cases now.
    @jridgewell
    jridgewell committed Feb 7, 2022
    Configuration menu
    Copy the full SHA
    5031a53 View commit details
    Browse the repository at this point in the history

  2. Update to remapping@2.1.0 to support source location override

    @jridgewell
    jridgewell committed Feb 7, 2022
    Configuration menu
    Copy the full SHA
    80ef63b View commit details
    Browse the repository at this point in the history