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

CSS sourcemap "sources" path is incorrect #19860

Closed
TimKraemer opened this issue May 8, 2016 · 5 comments
Closed

CSS sourcemap "sources" path is incorrect #19860

TimKraemer opened this issue May 8, 2016 · 5 comments

Comments

@TimKraemer
Copy link

Hi,

I'm not a web-developer so I might be missing something, but I think the "sources"-paths in all css.map files are wrong.
I fetched bootstrap via bower:
bower install bootstrap
wich results in a folder-structure like this:

bower_components
-> bootstrap
    -> dist
        -> css
            -> bootstrap.css.map
    -> less
       -> normalize.less
...

However bootstrap.css.map looks for less/normalize.less in its relative child-folder:

{
  "version":3,
  "sources":
      [ "bootstrap.css", "less/normalize.less", ... ]
...
}

Shouldn't this be "../../less/normalize.less" (which works in my setup)?

@cvrebert
Copy link
Collaborator

Fixing #19063 will also fix this.

@cvrebert cvrebert changed the title bower: css.map "sources"-path links to relative child folder CSS sourcemap "sources" path is incorrect May 11, 2016
@wolfy1339
Copy link
Contributor

You can add a sourceRoot option in the sourcemap to fix this

@TimKraemer
Copy link
Author

thanks @wolfy1339 - that worked for me (at least until the next update 😃)

@cvrebert cvrebert added this to the v3.3.7 milestone Jul 8, 2016
@cvrebert
Copy link
Collaborator

cvrebert commented Jul 8, 2016

Looks like we ought to set sourceMapBasepath: 'dist/css/'

@cvrebert cvrebert modified the milestones: v3.3.7, v3.3.8 Jul 25, 2016
@mdo
Copy link
Member

mdo commented Sep 5, 2016

Bootstrap 3 is no longer being officially developed or supported.

All work has moved onto our next major release, v4. As such, this issue or pull request is being closed as a "won't fix." For additional help and support, we recommend utilizing our community resources. Thanks for your understanding, and see you on the other side of v4!

<3,
@mdo and team

@mdo mdo closed this as completed Sep 5, 2016
@mdo mdo modified the milestone: v3.3.8 Sep 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants