sass-cli
I don’t want to install Ruby, but I want to compile *.scss from the command line.
Same here.
If you use the Ruby CLI, you will find some things missing. This command accepts two arguments, which may either be a pair of filenames or a pair of directory names.
Examples
Two files:
$ sass assets/scss/file.scss build/output.cssTwo dirs:
$ sass assets/scss build/css
1 maintainer
Metadata
1 maintainer
Release files for sass-cli 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sass-cli-0.0.3.tar.gz | 2.1 kB | Without provenance | Details |
Release files / sass-cli-0.0.3.tar.gz
| Download URL | sass-cli-0.0.3.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ccf5e346d40776cc6606f2d9ec86d42eaca20c9d925cb2cc0aa51b637c43b5b
|
|
BLAKE2b-256 checksum How to use checksums |
5068765a8fa98c214c8a6f3dd96e61386196c04bae5eb96a543c6f90cfded3a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sass-cli 0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
