seed-dash is a specialized utility pack designed for the Seed CSS framework, specifically addressing the manipulation of configuration variables within Sass, particularly for lists and maps. It implements a limited set of Underscore/lodash-like methods such as `_get`, `_set`, and `_extend` directly in Sass to facilitate dynamic configuration adjustments. Released at version 0.0.2, the project appears to be unmaintained, with its last known activity several years ago. The project's own documentation recommends `Sass Dash` for a more comprehensive Underscore/lodash-like experience in Sass, indicating that seed-dash is a niche or superseded solution for very specific Seed framework configuration tasks, rather than a general-purpose Sass utility library. It is designed to be integrated into a build pipeline, typically via Node.js tools like Gulp.
npm install seed-dashVerified import paths — ran on the pinned version, not inferred.
This example demonstrates how to integrate `seed-dash` into a Gulp-based Sass compilation pipeline, allowing Sass files to import and use its utility functions for configuration.
Consider migrating to actively maintained Sass utility libraries like `Sass Dash` (github.com/davidkpiano/sassdash) which offers a more robust and complete feature set and is still maintained.
Evaluate `Sass Dash` or other modern Sass utility libraries for new projects or refactoring existing ones that heavily rely on `seed-dash`'s specific behaviors.
Remember that `seed-dash`'s core functionality resides within the compiled Sass. The Node.js part only exposes paths. All utility calls (e.g., `_get`, `_set`) must occur within your `.scss` files.
Ensure that `gulp-sass` (or your chosen Sass compiler) is provided with an `includePaths` array that includes the result of `require('seed-dash')`. Example: `includePaths: require('seed-dash')`.Update your `gulp-sass` initialization: `const sass = require('gulp-sass')(require('sass'));` to ensure it uses a compatible Sass compiler.Use `sass` (Dart Sass) instead of `node-sass` for better Node.js version compatibility. If sticking with `node-sass`, ensure your Node.js version matches one supported by the specific `node-sass` version in your `node_modules`.
No dependency data recorded yet.