You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stylus currently resolves stylus files if they have the same name as their parent folder (with .styl extension).
For example:
given the following directory structure where test.styl is the input file and test.css is the output file
.
├── a
| ├── a.styl
├── test.styl
├── test.css
and the following file contents
./test.styl
@require a
./a/a.styl
bodybackground-colorred
yields the following output ./test.css
body {
background-color:#f00;
}
this seems like logical and intended behavior, but it appears to not be listed in the documentation ( or at least not in the @import.md index styles section:
@ import also supports index styles. This means when you @import blueprint, it will resolve eitherblueprint.styl or blueprint/index.styl. This is really useful for libraries that want to expose all their features, while still allowing feature subsets to be imported.
Unless this behavior is unintended, it should probably be changed to something like:
@ import also supports index styles. This means when you @import blueprint, it will resolve blueprint.styl, blueprint/index.styl, or blueprint/blueprint.styl . This is really useful for libraries that want to expose all their features, while still allowing feature subsets to be imported.
The text was updated successfully, but these errors were encountered:
Stylus currently resolves stylus files if they have the same name as their parent folder (with .styl extension).
For example:
given the following directory structure where
test.styl
is the input file andtest.css
is the output fileand the following file contents
./test.styl
@require a
./a/a.styl
yields the following output
./test.css
this seems like logical and intended behavior, but it appears to not be listed in the documentation ( or at least not in the @import.md index styles section:
Unless this behavior is unintended, it should probably be changed to something like:
The text was updated successfully, but these errors were encountered: