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.

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

source map generated by rollup miss 'file' property #986

Closed
ash0080 opened this issue Sep 25, 2016 · 5 comments · Fixed by #1223
Closed

source map generated by rollup miss 'file' property #986

ash0080 opened this issue Sep 25, 2016 · 5 comments · Fixed by #1223

Comments

@ash0080
Copy link

ash0080 commented Sep 25, 2016

I do not know if it's a bug, because it's too trivial...
The source map generated by rollup miss 'file' property like this

{"version":3,"file":null,"sources":["..

but, without the file name, WebStorm will ignore the source map, so you can't debug in it.
thought it's easy to be fixed manually, but with --watch, means very annoying.

rollup version 0.36.0 with rollup-plugin-typescript

@marvinhagemeister
Copy link

marvinhagemeister commented Sep 29, 2016

I'm running into a similar problem in the chrome debug extension for vscode which complains about not finding the correct file names.

EDIT: Curiously, the spec clearly states that the file property is optional

@ash0080
Copy link
Author

ash0080 commented Oct 1, 2016

@marvinhagemeister Yes, file property is optional, so you can debug it in Chrome, but seems the IDEs need the anchor to map the right files in source

@Rich-Harris
Copy link
Contributor

I can't reproduce this, is it still happening with the current version? If so, please include a repro – thanks

@gnomesley
Copy link

This only happens when using plugins.
Here is a repro: https://github.com/gnomesley/rollup-sourcemap-file

Rich-Harris added a commit that referenced this issue Jan 5, 2017
Rich-Harris added a commit that referenced this issue Jan 5, 2017
Populate file property of sourcemaps when plugins are involved
@Rich-Harris
Copy link
Contributor

Thanks — fixed in 0.40.2

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

Successfully merging a pull request may close this issue.

5 participants