Skip to content
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

[Bug] Directory structure difference between original bootstrap package and gem #288

Open
bogdan opened this issue Sep 9, 2024 · 0 comments

Comments

@bogdan
Copy link

bogdan commented Sep 9, 2024

I am looking to use some vendor code that imports individual CSS modules from bootstrap package.
It does it like so:

@import "bootstrap/scss/functions";
@import "bootstrap/scss/variables";
@import "bootstrap/scss/mixins";
@import "bootstrap/scss/reboot";

Countless examples: https://github.com/search?q=import+bootstrap%2Fscss%2Ffunctions&type=code

Those imports become broken when using the gem because gem has different directory structure and imports breaking all packages that relay on it. This gem is using a different dir structure and imports like:

@import "bootstrap/functions";
@import "bootstrap/variables";
@import "bootstrap/variables-dark";

https://github.com/twbs/bootstrap-rubygem/blob/main/assets/stylesheets/_bootstrap.scss#L7C1-L9C36

This can be fixed by adding a symlink or ideally follow original directory structure of bootstrap package.

@bogdan bogdan changed the title [Bug] Directory structure difference between original bootstrap package an gem [Bug] Directory structure difference between original bootstrap package and gem Sep 9, 2024
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

No branches or pull requests

1 participant