node-sass-yaml-importer

Features

• Added support for the modern Sass JavaScript API (until v7, only the legacy API was supported)
• Added first-class support for bundling with webpack/rspack through sass-loader

⚠️ Breaking Changes

• Requires at least Node.js 18
• Instead of exporting it as the single export, the legacy Sass JavaScript API importer is exported as legacyYamlImporter.
• Various utility functions that have previously been exposed (isYamlFile, parseValue, ...) are no longer available.

BREAKING:

• Handling of strings changed
• Drop support for Node.js < 14 (does still work for this release, but is no longer checked in tests)

https://github.com/loilo/node-sass-yaml-importer/compare/v6.0.1...v7.0.0

This is a release without any functionality changes, exclusively for bringing the latest README contents to npm.

https://github.com/loilo/node-sass-yaml-importer/compare/v6.0.0...v6.0.1

BREAKING:

All object keys are now quoted (c5e3c15). This will affect you if you use unquoted strings as object keys which Sass interprets as other value types (e.g. red is a color, 2fold is a number with a unit). An example can be found in the readme under Importing objects.

https://github.com/loilo/node-sass-yaml-importer/compare/v5.0.0...v6.0.0

BREAKING:

• Drop support for Node.js < v10
• Although undocumented: The exported isYAMLFile function has been renamed to isValidDataFile as it now also allows for JSON files.

Features:

• Allow importing JSON files ee8f389

Bugfixes:

• Generate trailing commas in all Sass lists and maps because Sass requires trailing commas to distinguish a single-item map from a list. 548a877

https://github.com/loilo/node-sass-yaml-importer/compare/v4.0.1...v5.0.0

• Use path.dirname() instead of custom implementation 70b40e4
• Fix missing quotes in Travis configuration 3085d15
• Update Node.js versions for Travis 0f2719e

https://github.com/Loilo/node-sass-yaml-importer/compare/v4.0.0...v4.0.1

BREAKING CHANGE:

• Drop support for Node.js v5

Also there are various development focused changes (ignited by a harsh npm audit report):

• Update and clean up dependencies
• Replace .npmignore with explicit files field
• Add engines field to package.json
• Improve .gitignore
• Sort package.json
• Remove yarn.lock