-
Notifications
You must be signed in to change notification settings - Fork 19
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
Bootstrap variant not working with latest bootstrap (5.2.0+) #315
Comments
the new version of bootstrap doesn't play nice with an old version of postcss-values-parser we're stuck with because webpacker this is significantly easier than migrating to shakapacker or jsbundling-rails see #315
fwiw I've opened #307 which moves us to shakapacker - so it sounds like if we could get that reviewed and landed it'd solve our problems? |
the new version of bootstrap doesn't play nice with an old version of postcss-values-parser we're stuck with because webpacker this is significantly easier than migrating to shakapacker or jsbundling-rails see #315
the new version of bootstrap doesn't play nice with an old version of postcss-values-parser we're stuck with because webpacker this is significantly easier than migrating to shakapacker or jsbundling-rails see #315
* Ensure secret key isn't in example.env fixes: #242 * Add instructions for generating a new key * Pin boostrap version the new version of bootstrap doesn't play nice with an old version of postcss-values-parser we're stuck with because webpacker this is significantly easier than migrating to shakapacker or jsbundling-rails see #315
@G-Rath I tested #307 locally and it also has this problem in the bootstrap variant. I think we should (for now) pin the bootstrap version to 5.1.3. @robotdana has done this as part of #313 |
The OP is now wrong because we're no longer using postcss - instead the error is about missing variables:
I've opened #320 which should fix this |
Overview
bootstrap 5.1.3 works fine but bootstrap 5.2.0 fails to
rails assets:precompile
. This will cause problems for anybody using the bootstrap variant and it will also cause CI to fail for any changes made from now on.assets:precompile output - click to expand
Cause
The bug is actually in the version of
postcss-values-parser
used by Webpacker. The bug is definitely inpostcss-values-parser
v2.0.1 but v6.0.2 is the current version (webpacker pulls in very old version)This is the postcss-values-parser issue: shellscape/postcss-values-parser#138
There are many changes between 5.1.3 and 5.2.0 - see twbs/bootstrap@v5.1.3...v5.2.0 so I'm not sure which lines are triggering the bug.
bootstrap
shipped a partial workaround but it doesn't seem to work - see twbs/bootstrap#35011Workarounds
If you need bootstrap for a project right now then the easiest fix is to lock to version
5.1.3
for now e.g.
What next?
Explore if we can update
postcss-values-parser
in our bundle without updatingwebpacker
. Alternatively perhaps moving to shakapacker would fix this by pulling in more modern dependencies.The text was updated successfully, but these errors were encountered: