You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a similar issue (described here in more detail) and found rework-npm to not be handling relative paths well. Playing around with what would fix it, if I change this line in getImport
to call path.resolve instead, it works fine for me.
The problem I saw was that by the time the file was being read here (if you follow the node modules down it's in atomify -> atomify-css -> rework -> css -> source-map-resolve in the lib/source-map-resolve-node.js file)
mapData.url is "../node_modules/bootstrap/dist/css/bootstrap.css.map" which would be right if it's read relative to the root directory that got passed into rework-npm. I verified the root directory that got passed in was my styles directory, where my css file lives. However, by the time the read happened, that root directory isn't used and instead was run using the cwd from the process which was my project root, so it's trying to find a node_modules directory as a peer to my project directory.
When I
@import
from an npm package whose stylesheet includes a relative link to a font, the font link is broken upon import.The text was updated successfully, but these errors were encountered: