Crates.io | stylance-cli |
lib.rs | stylance-cli |
version | 0.5.2 |
source | src |
created_at | 2024-01-08 14:22:26.589524 |
updated_at | 2024-10-30 15:24:22.848661 |
description | Cli tool for bundling stylance scoped CSS files. |
homepage | |
repository | https://github.com/basro/stylance-rs |
max_upload_size | |
id | 1092572 |
size | 36,862 |
Stylance-cli is the build tool for Stylance.
It reads your css module files and transforms them in the following way:
.class
will become .class-63gi2cY
):global(contents)
while leaving contents intact.Install stylance cli:
cargo install stylance-cli
Run stylance cli:
stylance ./path/to/crate/dir/ --output-file ./bundled.scss
The first argument is the path to the directory containing the Cargo.toml of your package/crate.
This will find all the files ending with .module.scss
and .module.css
and bundle them into ./bundled.scss
, all classes will be modified to include a hash that matches the one the import_crate_style!
macro produces.
Resulting ./bundled.scss
:
.header-f45126d {
background-color: red;
}
By default stylance cli will only look for css modules inside the crate's ./src/
folder. This can be configured.
output-dir
for better SASS compatibilityIf you plan to use the output of stylance in a SASS project (by importing it from a .scss file), then I recommend using the output-dir
option instead of output-file
.
stylance ./path/to/crate/dir/ --output-dir ./styles/
This will create the folder ./styles/stylance/
.
When using --output-dir (or output_dir in package.metadata.stylance) stylance will not bundle the transformed module files, instead it will create a "stylance" folder in the specified output-dir path which will contain all the transformed css modules inside as individual files.
This "stylance" folder also includes an _index.scss file that imports all the transformed scss modules.
You can then use @use "path/to/the/folder/stylance"
to import the css modules into your sass project.
During development it is convenient to use sylance cli in watch mode:
stylance --watch --output-file ./bundled.scss ./path/to/crate/dir/
The stylance process will then watch any .module.css
and .module.scss
files for changes and automatically rebuild the output file.
Stylance configuration lives inside the Cargo.toml file of your crate.
All configuration settings are optional.
[package.metadata.stylance]
# output_file
# When set, stylance-cli will bundle all css module files
# into by concatenating them and put the result in this file.
output_file = "./styles/bundle.scss"
# output_dir
# When set, stylance-cli will create a folder named "stylance" inside
# the output_dir directory.
# The stylance folder will be populated with one file per detected css module
# and one _all.scss file that contains one `@use "file.module-hash.scss";` statement
# per module file.
# You can use that file to import all your modules into your main scss project.
output_dir = "./styles/"
# folders
# folders in which stylance cli will look for css module files.
# defaults to ["./src/"]
folders = ["./src/", "./styles/"]
# extensions
# files ending with these extensions will be considered to be
# css modules by stylance cli and will be included in the output
# bundle
# defaults to [".module.scss", ".module.css"]
extensions = [".module.scss", ".module.css"]
# scss_prelude
# When generating an scss file stylance-cli will prepend this string
# Useful to include a @use statement to all scss modules.
scss_prelude = '@use "../path/to/prelude" as *;'
# hash_len
# Controls how long the hash name used in scoped classes should be.
# It is safe to lower this as much as you want, stylance cli will produce an
# error if two files end up with colliding hashes.
# defaults to 7
hash_len = 7
# class_name_pattern
# Controls the shape of the transformed scoped class names.
# [name] will be replaced with the original class name
# [hash] will be replaced with the hash of css module file path.
# defaults to "[name]-[hash]"
class_name_pattern = "my-project-[name]-[hash]"