Skip to content

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

@bogdan

Description

@bogdan

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions