Skip to content
This repository has been archived by the owner on Aug 4, 2021. It is now read-only.
This repository has been archived by the owner on Aug 4, 2021. It is now read-only.

sourcemap is likely to be incorrect #132

Closed
goumang2010 opened this issue Mar 28, 2017 · 5 comments
Closed

sourcemap is likely to be incorrect #132

goumang2010 opened this issue Mar 28, 2017 · 5 comments

Comments

@goumang2010
Copy link

In babel plugin options, I ignore some files, then rollup tell me:

Sourcemap is likely to be incorrect: a plugin ('babel') was used to transform files, but didn't generate a sourcemap for the transformation.

And the generated sourcemap is wrong indeed(not contain the ignore files)
How can I get the full sourcemap that includes the ignored files of babel plugin?

The following is my babel plugin option:

{
    babelrc: false,
    "presets": [
        ["latest", {
            "es2015": {
                "modules": false
            }
        }]
    ],
    "ignore": [
        "dist/*.js",
        "vendor.js"
    ],
    "plugins": [
        "external-helpers"
    ],
    externalHelpers: true
}
@Andarist
Copy link
Member

Closing this as outdated, I hope you have resolved your issue by now. If not - feel free to open new issue.

@ssimpo
Copy link

ssimpo commented Aug 20, 2018

@goumang2010 Did you fix this then. I am getting the exact same problem on new version of this plugin (4.0.0-beta.4). Exactly the same thing:

Sourcemap is likely to be incorrect: a plugin ('babel') was used to transform files, but didn't generate a sourcemap for the transformation.

After added an ignore.

@Andarist
Copy link
Member

@ssimpo could u create a simple repro?

@ssimpo
Copy link

ssimpo commented Aug 24, 2018

@Andarist I in the middle of a project right now but will try to in the next few weeks. So, sorry for commenting then offering no further help! Since, there are only two people commenting here I figure it can't be super urgent (probably something obscure we are both doing that triggers it).

I'll also, have a dig around to see if I can see where it is coming from. The project I am getting these errors on is quite large and would have to extract some sort of test repo. I can probably reproduce some of the work flow that is generating this in a test repo to see if the error is reproduced.

@thisconnect
Copy link

I created an example repo, I am hero :P and opened a new issue

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants