Skip to content

Conversation

@junket
Copy link

@junket junket commented Nov 19, 2024

From version 0.5.0 to 0.6.0, bulma.min.css was vendored into the lib instead of linking to the CDN version to better conform to the content security policy.

Unfortunately, when passing through a common older CSS bundler (sass-rails) during rails assets:precompile, that CSS doesn't seem to pass muster:

SassC::SyntaxError: Error: Invalid CSS after "...--s),var(--l));": expected "}", was "--00-l:var(--bulma-" (SassC::SyntaxError)

I assume Bulma is using some feature of DartSass/CSS that sass-rails and sassc-rails do not support. Updating the CSS bundler to dartsass-rails fixes the issue.

From version 0.5.0 to 0.6.0, `bulma.min.css` was vendored into the lib instead of linking to the CDN version to better conform to the content security policy.

Unfortunately, when passing through a common older CSS bundler (sass-rails) during `rails assets:precompile`, that CSS doesn't seem to pass muster:
```
SassC::SyntaxError: Error: Invalid CSS after "...--s),var(--l));": expected "}", was "--00-l:var(--bulma-" (SassC::SyntaxError)
```

I assume Bulma is using some feature of DartSass/CSS that `sass-rails` and `sassc-rails` do not support. Updating the CSS bundler to `dartsass-rails` fixes the issue.
@rosa
Copy link
Member

rosa commented Nov 19, 2024

Ohh, great catch, explanation and change! Thank you so much!

@rosa rosa merged commit ac664d8 into rails:main Nov 19, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants