-
Notifications
You must be signed in to change notification settings - Fork 103
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
InvalidMappingColumn
for mapped eol.
#179
Comments
I don't think it's possible to detect that source map reference EOL when |
Use |
thank you very much for the fast response! |
…ck to work around thrwon error see danvk/source-map-explorer#179 for the error and reason
…ck to work around thrwon error see danvk/source-map-explorer#179 for the error and reason
Description
Sometimes during compilation of files, some plugins will add an eol to the end of the output. e.g. mini-css-extract-plugin. During the source-map generation (e.g. by mozilla/source-map) a new segment will be added for the line ending without a reference to the original source (probably because the eol didn't come from the source). Which according to the source-map spec, segments with only one variable are allowed.
source-map-explorer when reading such a source-map throws InvalidMappingColumn error with the message:
might be related to #136
Steps to reproduce
css:
source-map:
run source-map-explorer with these files
Files to reproduce
minimal repo: https://github.com/mbehzad/webpack-postcss-cssnano-source-map-issue
Expected behavior
it would be great if source-map-explorer could detect that the column number bing one bigger that the line length and having no reference for the original source is because of a eol and ignore it.
Environment
Additional context
output was generated by a webpack build using mini-css-extract-plugin and the css file was minified prior / as part of that.
The text was updated successfully, but these errors were encountered: