sass-graph
npmv4.0.1Parse sass files and extract a graph of imports
Not recommended for new projects
No — sass-graph should not be adopted for new projects. Last published 1470 days ago. Pulls in 21 transitive packages, about 4.7 MB installed (at least — some of the tree is still being crawled).
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1470 days ago.
- CWeight: grade C, Fair — worth a look.
Pulls in 21 transitive packages, about 4.7 MB installed (at least — some of the tree is still being crawled).
- ASupply chain: grade A, Excellent.
No install scripts, 2 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding sass-graph to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Licenses in the dependency tree
Every license you inherit by installing sass-graph, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=12
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the sass-graph README.
var sassGraph = require('./sass-graph');sass-graph vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| sass-graphthis page | 0 | 1 | MIT | 4 years ago |
| node-sassdeprecated | 888.4K | 0 | MIT | 1 day ago |
| sass | 0 | 4 | MIT | 1 day ago |
| scss-tokenizer | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by sass-graph v4.0.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (5)
Used by
Popular packages that depend on sass-graph.
Relationship graph
Dependencies (left) and dependents (right) of sass-graph.
Frequently installed together
Lodash modular utilities.
An AST-based pattern checker for JavaScript.
CLI app helper
Opinionated, caching, retrying fetch client
A globbing fs.watch wrapper built from the best parts of other fine watch libs.
An optionally-asynchronous forEach with an interesting interface.
Given a possibly case-variant version of an existing filesystem path, returns the case-exact, normalized version as stored in the filesystem.
Native Abstractions for Node.js: C++ header for Node 0.8 -> 26 compatibility
the most correct and second fastest glob implementation in JavaScript
Cross platform child_process#spawn and child_process#spawnSync
Non-blocking stdout stream
Release history
No releases in the last two years, typically about 100 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 4.0.1latest | 4 years ago | 14 KB | MIT |
| 4.0.0 | 4 years ago | 18 KB | MIT |
| 3.0.5 | 6 years ago | 17 KB | MIT |
| 2.2.6 | 6 years ago | 15 KB | MIT |
| 2.2.5 | 6 years ago | 15 KB | MIT |
| 3.0.4 | 7 years ago | 17 KB | MIT |
| 3.0.3 | 8 years ago | 17 KB | MIT |
| 3.0.2 | 8 years ago | 17 KB | MIT |
| 3.0.1 | 8 years ago | 17 KB | MIT |
| 3.0.0 | 8 years ago | 16 KB | MIT |
| 2.2.4 | 9 years ago | — | MIT |
| 2.2.3 | 9 years ago | — | MIT |
| 2.2.2 | 9 years ago | — | MIT |
| 2.2.1 | 9 years ago | — | MIT |
| 2.2.0 | 9 years ago | — | MIT |
Overview
sass-graph is an npm package that parse sass files and extract a graph of imports. It has 1 known dependents in the graph. The latest version is 4.0.1, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need parse sass files and extract a graph of imports and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Frequently asked questions
Should I use sass-graph?
No — sass-graph should not be adopted for new projects. Last published 1470 days ago. Pulls in 21 transitive packages, about 4.7 MB installed (at least — some of the tree is still being crawled).
How do I install sass-graph?
Run `npm install sass-graph` to add sass-graph to your npm project.
How many dependencies does sass-graph have?
sass-graph declares 9 direct dependencies and pulls in 21 packages in total once its runtime tree is resolved totalling about 4.7 MB on disk.
What license is sass-graph released under?
sass-graph is distributed under the MIT license. Its dependency tree also includes: BSD-3-Clause, BlueOak-1.0.0, ISC, MIT.
How popular is sass-graph?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on sass-graph.
Is sass-graph still maintained?
The most recent release of sass-graph (v4.0.1) was published 4 years ago.
Does sass-graph run install scripts?
No. sass-graph does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.