-
Notifications
You must be signed in to change notification settings - Fork 247
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
Yarn, asset-pipeline and .css.map #411
Comments
yea.. i'm having the same issue.. with multiple css.map files |
This is still happening in Rails 6.rc1 and sprockets-rails 3.2.1. I solved it for now by importing from |
@dennyluan i did the same to get rid of the error |
Hi, i'm having the same issue but with .min.js files
but then when I open the devtools on Chrome, console shows an error
Any idea how can I solve this? |
I also encountered a similar situation. It may not be a fundamental solution, but I decided to use the sprockets processor to remove all sourceMappingURL in .css file. The code looks like below.
|
Hi there,
I'm a very happy user of the aforementioned technologies and very grateful for the contributors. I've noticed a small issue that I was hoping to report when using Rails 5.1.4. One of my assets points to a sourcemap and I'm having problems telling Rails where to look for it. Since Rails doesn't know where to find it, it throws an error in the console :(.
Whenever I visit any page, I get
What's the best way to inform the asset pipeline of a sourcemap? The directory looks like...
The bottom of the CSS has:
My package.json looks like...
And my application.js...
The text was updated successfully, but these errors were encountered: