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 am using yarn with my rails 5.1 app (not webpacker, just the default asset pipeline).
Running a local server in development environment, I experience no issues with my assets.
But as soon as I precompile my assets (the environment doesn't matter) or let Heroku package my assets, all stylesheets (of node modules) I imported from within my application.sass file don't work anymore.
The reason for that behavior is that sass compiles all files into one output file, but because of some reason appears to miss the @import statements, which include node modules and loads these files separately.
I am using yarn with my rails 5.1 app (not webpacker, just the default asset pipeline).
Running a local server in development environment, I experience no issues with my assets.
But as soon as I precompile my assets (the environment doesn't matter) or let Heroku package my assets, all stylesheets (of node modules) I imported from within my
application.sass
file don't work anymore.The reason for that behavior is that sass compiles all files into one output file, but because of some reason appears to miss the
@import
statements, which include node modules and loads these files separately.So this:
Compiles to this in development:
and to this in production:
while loading
node_module/nodemodule.css
separately as an asset, but the browser cannot resolve it.The text was updated successfully, but these errors were encountered: