[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-9146":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":29,"readmeContent":30,"aiSummary":31,"trendingCount":16,"starSnapshotCount":16,"syncStatus":18,"lastSyncTime":32,"discoverSource":33},9146,"dart-sass","sass\u002Fdart-sass","sass","The reference implementation of Sass, written in Dart.","https:\u002F\u002Fsass-lang.com\u002Fdart-sass",null,"Dart",4192,376,71,63,0,1,2,6,3,29.73,"MIT License",false,"main",true,[27,28,5,7],"css-preprocessor","dart","2026-06-12 02:02:03","A [Dart][dart] implementation of [Sass][sass]. **Sass makes CSS fun**.\n\n\u003Ctable>\n  \u003Ctr>\n    \u003Ctd>\n      \u003Cimg width=\"118px\" alt=\"Sass logo\" src=\"https:\u002F\u002Frawgit.com\u002Fsass\u002Fsass-site\u002Fmain\u002Fsource\u002Fassets\u002Fimg\u002Flogos\u002Flogo.svg\" \u002F>\n    \u003C\u002Ftd>\n    \u003Ctd valign=\"middle\">\n      \u003Ca href=\"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsass\">\u003Cimg width=\"100%\" alt=\"npm statistics\" src=\"https:\u002F\u002Fnodei.co\u002Fnpm\u002Fsass.png?downloads=true\">\u003C\u002Fa>\n    \u003C\u002Ftd>\n    \u003Ctd valign=\"middle\">\n      \u003Ca href=\"https:\u002F\u002Fpub.dartlang.org\u002Fpackages\u002Fsass\">\u003Cimg alt=\"Pub version\" src=\"https:\u002F\u002Fimg.shields.io\u002Fpub\u002Fv\u002Fsass.svg\">\u003C\u002Fa>\n      \u003Cbr>\n      \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsass\u002Fdart-sass\u002Factions\">\u003Cimg alt=\"GitHub actions build status\" src=\"https:\u002F\u002Fgithub.com\u002Fsass\u002Fdart-sass\u002Fworkflows\u002FCI\u002Fbadge.svg\">\u003C\u002Fa>\n    \u003C\u002Ftd>\n    \u003Ctd>\n      \u003Ca href=\"https:\u002F\u002Ffront-end.social\u002F@sass\">\u003Cimg alt=\"@sass@front-end.social on Fediverse\" src=\"https:\u002F\u002Fimg.shields.io\u002Fmastodon\u002Ffollow\u002F110159358073946175?domain=https%3A%2F%2Ffront-end.social\">\u003C\u002Fa>\n      \u003Cbr>\n      \u003Ca href=\"https:\u002F\u002Ftwitter.com\u002FSassCSS\">\u003Cimg alt=\"@SassCSS on Twitter\" src=\"https:\u002F\u002Fimg.shields.io\u002Ftwitter\u002Ffollow\u002FSassCSS?label=%40SassCSS&style=social\">\u003C\u002Fa>\n      \u003Cbr>\n      \u003Ca href=\"https:\u002F\u002Fstackoverflow.com\u002Fquestions\u002Ftagged\u002Fsass\">\u003Cimg alt=\"stackoverflow\" src=\"https:\u002F\u002Fimg.shields.io\u002Fstackexchange\u002Fstackoverflow\u002Ft\u002Fsass?label=Sass%20questions&logo=stackoverflow&style=social\">\u003C\u002Fa>\n      \u003Cbr>\n      \u003Ca href=\"https:\u002F\u002Fgitter.im\u002Fsass\u002Fsass?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge\">\u003Cimg alt=\"Gitter\" src=\"https:\u002F\u002Fimg.shields.io\u002Fgitter\u002Froom\u002Fsass\u002Fsass?label=chat&logo=gitter&style=social\">\u003C\u002Fa>\n    \u003C\u002Ftd>\n  \u003C\u002Ftr>\n\u003C\u002Ftable>\n\n[dart]: https:\u002F\u002Fwww.dartlang.org\n[sass]: https:\u002F\u002Fsass-lang.com\u002F\n\n* [Using Dart Sass](#using-dart-sass)\n  * [From Chocolatey or Scoop (Windows)](#from-chocolatey-or-scoop-windows)\n  * [From Homebrew (macOS)](#from-homebrew-macos-or-linux)\n  * [Standalone](#standalone)\n  * [From npm](#from-npm)\n    * [Dart Sass in the Browser](#dart-sass-in-the-browser)\n    * [Legacy JavaScript API](#legacy-javascript-api)\n    * [Using Sass with Jest](#using-sass-with-jest)\n  * [From Pub](#from-pub)\n    * [`sass_api` Package](#sass_api-package)\n  * [From Source](#from-source)\n  * [In Docker](#in-docker)\n* [Why Dart?](#why-dart)\n* [Compatibility Policy](#compatibility-policy)\n  * [Browser Compatibility](#browser-compatibility)\n  * [Node.js Compatibility](#nodejs-compatibility)\n  * [Invalid CSS](#invalid-css)\n* [Embedded Dart Sass](#embedded-dart-sass)\n  * [Usage](#usage)\n* [Behavioral Differences from Ruby Sass](#behavioral-differences-from-ruby-sass)\n\n## Using Dart Sass\n\nThere are a few different ways to install and run Dart Sass, depending on your\nenvironment and your needs.\n\n### From Chocolatey or Scoop (Windows)\n\nIf you use [the Chocolatey package manager](https:\u002F\u002Fchocolatey.org\u002F)\nor [the Scoop package manager](https:\u002F\u002Fgithub.com\u002Flukesampson\u002Fscoop) for\nWindows, you can install Dart Sass by running\n\n```cmd\nchoco install sass\n```\n\nor\n\n```cmd\nscoop install sass\n```\n\nThat'll give you a `sass` executable on your command line that will run Dart\nSass. See [the CLI docs][cli] for details.\n\n[cli]: https:\u002F\u002Fsass-lang.com\u002Fdocumentation\u002Fcli\u002Fdart-sass\n\n### From Homebrew (macOS or Linux)\n\nIf you use [the Homebrew package manager](https:\u002F\u002Fbrew.sh\u002F), you\ncan install Dart Sass by running\n\n```sh\nbrew install sass\u002Fsass\u002Fsass\n```\n\nThat'll give you a `sass` executable on your command line that will run Dart\nSass.\n\n### Standalone\n\nYou can download the standalone Dart Sass archive for your operating\nsystem—containing the Dart VM and the snapshot of the executable—from [the\nGitHub release page][]. Extract it, [add the directory to your path][], restart\nyour terminal, and the `sass` executable is ready to run!\n\n[the GitHub release page]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fdart-sass\u002Freleases\u002F\n[add the directory to your path]: https:\u002F\u002Fkatiek2.github.io\u002Fpath-doc\u002F\n\n### From npm\n\nDart Sass is available, compiled to JavaScript, [as an npm package][npm]. You\ncan install it globally using `npm install -g sass` which will provide access to\nthe `sass` executable. You can also add it to your project using\n`npm install --save-dev sass`. This provides the executable as well as a\nlibrary:\n\n[npm]: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsass\n\n```js\nconst sass = require('sass');\n\nconst result = sass.compile(scssFilename);\n\n\u002F\u002F OR\n\n\u002F\u002F Note that `compileAsync()` is substantially slower than `compile()`.\nconst result = await sass.compileAsync(scssFilename);\n```\n\nSee [the Sass website][js api] for full API documentation.\n\n[js api]: https:\u002F\u002Fsass-lang.com\u002Fdocumentation\u002Fjs-api\n\n#### Dart Sass in the Browser\n\nThe `sass` npm package can also be run directly in the browser. It's compatible\nwith all major web bundlers as long as you disable renaming (such as\n[`--keep-names`] in esbuild). You can also import it directly from a browser as\nan ECMAScript Module without any bundling (assuming `node_modules` is served as\nwell):\n\n[`--keep-names`]: https:\u002F\u002Fesbuild.github.io\u002Fapi\u002F#keep-names\n\n```html\n\u003Cscript type=\"importmap\">\n  {\n    \"imports\": {\n      \"immutable\": \".\u002Fnode_modules\u002Fimmutable\u002Fdist\u002Fimmutable.es.js\",\n      \"sass\": \".\u002Fnode_modules\u002Fsass\u002Fsass.default.js\"\n    }\n  }\n\u003C\u002Fscript>\n\n\u003C!-- Support browsers like Safari 16.3 without import maps support. -->\n\u003Cscript async src=\"https:\u002F\u002Funpkg.com\u002Fes-module-shims@^1.7.0\" crossorigin=\"anonymous\">\u003C\u002Fscript>\n\n\u003Cscript type=\"module\">\n  import * as sass from 'sass';\n\n  console.log(sass.compileString(`\n    .box {\n      width: 10px + 15px;\n    }\n  `));\n\u003C\u002Fscript>\n```\n\nOr from a CDN:\n\n```html\n\u003Cscript type=\"importmap\">\n  {\n    \"imports\": {\n      \"immutable\": \"https:\u002F\u002Funpkg.com\u002Fimmutable@^4.0.0\",\n      \"sass\": \"https:\u002F\u002Funpkg.com\u002Fsass@^1.63.0\u002Fsass.default.js\"\n    }\n  }\n\u003C\u002Fscript>\n\n\u003C!-- Support browsers like Safari 16.3 without import maps support. -->\n\u003Cscript async src=\"https:\u002F\u002Funpkg.com\u002Fes-module-shims@^1.7.0\" crossorigin=\"anonymous\">\u003C\u002Fscript>\n\n\u003Cscript type=\"module\">\n  import * as sass from 'sass';\n\n  console.log(sass.compileString(`\n    .box {\n      width: 10px + 15px;\n    }\n  `));\n\u003C\u002Fscript>\n```\n\nOr even bundled with all its dependencies:\n\n```html\n\u003Cscript type=\"module\">\n  import * as sass from 'https:\u002F\u002Fjspm.dev\u002Fsass';\n\n  console.log(sass.compileString(`\n    .box {\n      width: 10px + 15px;\n    }\n  `));\n\u003C\u002Fscript>\n```\n\nSince the browser doesn't have access to the filesystem, the [`compile()`] and\n`compileAsync()` functions aren't available for it. If you want to load other\nfiles, you'll need to pass a [custom importer] to [`compileString()`] or\n[`compileStringAsync()`]. The [legacy API] is also not supported in the browser.\n\n[`compile()`]: https:\u002F\u002Fsass-lang.com\u002Fdocumentation\u002Fjs-api\u002Ffunctions\u002Fcompile\n[`compileAsync()`]: https:\u002F\u002Fsass-lang.com\u002Fdocumentation\u002Fjs-api\u002Ffunctions\u002FcompileAsync\n[custom importer]: https:\u002F\u002Fsass-lang.com\u002Fdocumentation\u002Fjs-api\u002Finterfaces\u002Fstringoptions\u002F#importer\n[`compileString()`]: https:\u002F\u002Fsass-lang.com\u002Fdocumentation\u002Fjs-api\u002Ffunctions\u002FcompileString\n[`compileStringAsync()`]: https:\u002F\u002Fsass-lang.com\u002Fdocumentation\u002Fjs-api\u002Ffunctions\u002FcompileStringAsync\n[legacy API]: #legacy-javascript-api\n\n#### Legacy JavaScript API\n\nDart Sass also supports an older JavaScript API that's fully compatible with\n[Node Sass] (with a few exceptions listed below), with support for both the\n[`render()`] and [`renderSync()`] functions. This API is considered deprecated\nand will be removed in Dart Sass 2.0.0, so it should be avoided in new projects.\n\n[Node Sass]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fnode-sass\n[`render()`]: https:\u002F\u002Fsass-lang.com\u002Fdocumentation\u002Fjs-api\u002Ffunctions\u002Frender\n[`renderSync()`]: https:\u002F\u002Fsass-lang.com\u002Fdocumentation\u002Fjs-api\u002Ffunctions\u002FrenderSync\n\nSass's support for the legacy JavaScript API has the following limitations:\n\n* Only the `\"expanded\"` and `\"compressed\"` values of [`outputStyle`] are\n  supported.\n\n* Dart Sass doesn't support the [`precision`] option. Dart Sass defaults to a\n  sufficiently high precision for all existing browsers, and making this\n  customizable would make the code substantially less efficient.\n\n* Dart Sass doesn't support the [`sourceComments`] option. Source maps are the\n  recommended way of locating the origin of generated selectors.\n\n[`outputStyle`]: https:\u002F\u002Fsass-lang.com\u002Fdocumentation\u002Fjs-api\u002Finterfaces\u002FLegacySharedOptions#outputStyle\n[`precision`]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fnode-sass#precision\n[`sourceComments`]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fnode-sass#sourcecomments\n\n#### Using Sass with Jest\n\nIf you're using [Jest] to run your tests, be aware that it has a [longstanding\nbug] where its default test environment breaks JavaScript's built-in\n[`instanceof` operator]. Dart Sass's JS package uses `instanceof` fairly\nheavily, so in order to avoid breaking Sass you'll need to install\n[`jest-environment-node-single-context`] and add `testEnvironment:\n'jest-environment-node-single-context'` to your Jest config.\n\n[Jest]: https:\u002F\u002Fjestjs.io\u002F\n[longstanding bug]: https:\u002F\u002Fgithub.com\u002Ffacebook\u002Fjest\u002Fissues\u002F2549\n[`instanceof` operator]: https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FJavaScript\u002FReference\u002FOperators\u002Finstanceof\n[`jest-environment-node-single-context`]: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fjest-environment-node-single-context\n\n### From Pub\n\nIf you're a Dart user, you can install Dart Sass globally using `pub global\nactivate sass`, which will provide a `sass` executable. You can also add it to\nyour pubspec and use it as a library. We strongly recommend importing it with\nthe prefix `sass`:\n\n```dart\nimport 'package:sass\u002Fsass.dart' as sass;\n\nvoid main(List\u003CString> args) {\n  print(sass.compile(args.first));\n}\n```\n\nSee [the Dart API docs][api] for details.\n\n[api]: https:\u002F\u002Fwww.dartdocs.org\u002Fdocumentation\u002Fsass\u002Flatest\u002Fsass\u002Fsass-library.html\n\n#### `sass_api` Package\n\nDart users also have access to more in-depth APIs via the [`sass_api` package].\nThis provides access to the Sass AST and APIs for resolving Sass loads without\nrunning a full compilation. It's separated out into its own package so that it\ncan increase its version number independently of the main `sass` package.\n\n[`sass_api` package]: https:\u002F\u002Fpub.dev\u002Fpackages\u002Fsass_api\n\n### From Source\n\nAssuming you've already checked out this repository:\n\n1. [Install Dart](https:\u002F\u002Fwww.dartlang.org\u002Finstall). If you download an archive\n   manually rather than using an installer, make sure the SDK's `bin` directory\n   is on your `PATH`.\n\n2. [Install Buf]. This is used to build the protocol buffers for the [embedded\n   compiler].\n\n3. In this repository, run `dart pub get`. This will install Dart Sass's\n   dependencies.\n\n4. Run `dart run grinder protobuf`. This will download and build the embedded\n   protocol definition.\n\n5. Run `dart bin\u002Fsass.dart path\u002Fto\u002Ffile.scss`.\n\n[Install Buf]: https:\u002F\u002Fdocs.buf.build\u002Finstallation\n[embedded compiler]: #embedded-dart-sass\n\nThat's it!\n\n### In Docker\n\nYou can install and run Dart Sass within Docker using the following Dockerfile\ncommands:\n\n```Dockerfile\n# Dart stage\nFROM bufbuild\u002Fbuf AS buf\nFROM dart:stable AS dart\n\n# Add your scss files\nCOPY --from=another_stage \u002Fapp \u002Fapp\n\n# Include Protocol Buffer binary\nCOPY --from=buf \u002Fusr\u002Flocal\u002Fbin\u002Fbuf \u002Fusr\u002Flocal\u002Fbin\u002F\n\nWORKDIR \u002Fdart-sass\nRUN git clone https:\u002F\u002Fgithub.com\u002Fsass\u002Fdart-sass.git . && \\\n  dart pub get && \\\n  dart run grinder protobuf\n# This is where you run sass.dart on your scss file(s)\nRUN dart .\u002Fbin\u002Fsass.dart \u002Fapp\u002Fsass\u002Fexample.scss \u002Fapp\u002Fpublic\u002Fcss\u002Fexample.css\n```\n\n## Why Dart?\n\nDart Sass has replaced Ruby Sass as the canonical implementation of the Sass\nlanguage. We chose Dart because it presented a number of advantages:\n\n* It's fast. The Dart VM is highly optimized, and getting faster all the time\n  (for the latest performance numbers, see [`perf.md`][perf]). It's much faster\n  than Ruby, and close to par with C++.\n\n* It's portable. The Dart VM has no external dependencies and can compile\n  applications into standalone snapshot files, so we can distribute Dart Sass as\n  only three files (the VM, the snapshot, and a wrapper script). Dart can also\n  be compiled to JavaScript, which makes it easy to distribute Sass through npm,\n  which the majority of our users use already.\n\n* It's easy to write. Dart is a higher-level language than C++, which means it\n  doesn't require lots of hassle with memory management and build systems. It's\n  also statically typed, which makes it easier to confidently make large\n  refactors than with Ruby.\n\n* It's friendlier to contributors. Dart is substantially easier to learn than\n  Ruby, and many Sass users in Google in particular are already familiar with\n  it. More contributors translates to faster, more consistent development.\n\n[perf]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fdart-sass\u002Fblob\u002Fmaster\u002Fperf.md\n\n## Compatibility Policy\n\nFor the most part, Dart Sass follows [semantic versioning][]. We consider all of\nthe following to be part of the versioned API:\n\n[semantic versioning]: https:\u002F\u002Fsemver.org\u002F\n\n* The Sass language semantics implemented by Dart Sass.\n* The Dart API.\n* The JavaScript API.\n* The command-line interface.\n\nBecause Dart Sass has a single version that's shared across the Dart,\nJavaScript, and standalone distributions, this may mean that we increment the\nmajor version number when there are in fact no breaking changes for one or more\ndistributions. However, we will attempt to limit the number of breaking changes\nwe make and group them in as few releases as possible to minimize churn. We\nstrongly encourage users to use [the changelog][] for a full understanding of\nall the changes in each release.\n\n[the changelog]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fdart-sass\u002Fblob\u002Fmaster\u002FCHANGELOG.md\n\nThere is one exception where breaking changes may be made outside of a major\nversion revision. It is occasionally the case that CSS adds a feature that's\nincompatible with existing Sass syntax in some way. Because Sass is committed to\nfull CSS compatibility, we occasionally need to break compatibility with old\nSass code in order to remain compatible with CSS.\n\nIn these cases, we will first release a version of Sass that emits deprecation\nwarnings for any stylesheets whose behavior will change. Then, at least three\nmonths after the release of a version with these deprecation warnings, we will\nrelease a minor version with the breaking change to the Sass language semantics.\n\n### Browser Compatibility\n\nIn general, we consider any change to Dart Sass's CSS output that would cause\nthat CSS to stop working in a real browser to be a breaking change. However,\nthere are some cases where such a change would have substantial benefits and\nwould only negatively affect a small minority of rarely-used browsers. We don't\nwant to have to block such a change on a major version release.\n\nAs such, if a change would break compatibility with less than 2% of the global\nmarket share of browser according to [StatCounter GlobalStats][], we may release\na minor version of Dart Sass with that change.\n\n[StatCounter GlobalStats]: https:\u002F\u002Fgs.statcounter.com\u002F\n\n### Node.js Compatibility\n\nWe consider dropping support for a given version of Node.js to be a breaking\nchange *as long as* that version is still supported by Node.js. This means that\nreleases listed as Current, Active LTS, or Maintenance LTS according to [the\nNode.js release page][]. Once a Node.js version is out of LTS, Dart Sass\nconsiders itself free to break support if necessary.\n\n[the Node.js release page]: https:\u002F\u002Fnodejs.org\u002Fen\u002Fabout\u002Fprevious-releases\n\n### Invalid CSS\n\nChanges to the behavior of Sass stylesheets that produce invalid CSS output are\n_not_ considered breaking changes. Such changes are almost always necessary when\nadding support for new CSS features, and delaying all such features until a new\nmajor version would be unduly burdensome for most users.\n\nFor example, when Sass began parsing `calc()` expressions, the invalid\nexpression `calc(1 +)` became a Sass error where before it was passed through\nas-is. This was not considered a breaking change, because `calc(1 +)` was never\nvalid CSS to begin with.\n\n## Embedded Dart Sass\n\nDart Sass includes an implementation of the compiler side of the [Embedded Sass\nprotocol]. It's designed to be embedded in a host language, which then exposes\nan API for users to invoke Sass and define custom functions and importers.\n\n[Embedded Sass protocol]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fblob\u002Fmain\u002Fspec\u002Fembedded-protocol.md\n\n### Usage\n\n* `sass --embedded` starts the embedded compiler and listens on stdin.\n* `sass --embedded --version` prints `versionResponse` with `id = 0` in JSON and\n  exits.\n\nThe `--embedded` command-line flag is not available when you install Dart Sass\nas an [npm package]. No other command-line flags are supported with\n`--embedded`.\n\n[npm package]: #from-npm\n\n## Behavioral Differences from Ruby Sass\n\nThere are a few intentional behavioral differences between Dart Sass and Ruby\nSass. These are generally places where Ruby Sass has an undesired behavior, and\nit's substantially easier to implement the correct behavior than it would be to\nimplement compatible behavior. These should all have tracking bugs against Ruby\nSass to update the reference behavior.\n\n1. `@extend` only accepts simple selectors, as does the second argument of\n   `selector-extend()`. See [issue 1599][].\n\n2. Subject selectors are not supported. See [issue 1126][].\n\n3. Pseudo selector arguments are parsed as `\u003Cdeclaration-value>`s rather than\n   having a more limited custom parsing. See [issue 2120][].\n\n4. The numeric precision is set to 10. See [issue 1122][].\n\n5. The indented syntax parser is more flexible: it doesn't require consistent\n   indentation across the whole document. See [issue 2176][].\n\n6. Colors do not support channel-by-channel arithmetic. See [issue 2144][].\n\n7. Unitless numbers aren't `==` to unit numbers with the same value. In\n   addition, map keys follow the same logic as `==`-equality. See\n   [issue 1496][].\n\n8. `rgba()` and `hsla()` alpha values with percentage units are interpreted as\n   percentages. Other units are forbidden. See [issue 1525][].\n\n9. Too many variable arguments passed to a function is an error. See\n   [issue 1408][].\n\n10. Allow `@extend` to reach outside a media query if there's an identical\n    `@extend` defined outside that query. This isn't tracked explicitly, because\n    it'll be irrelevant when [issue 1050][] is fixed.\n\n11. Some selector pseudos containing placeholder selectors will be compiled\n    where they wouldn't be in Ruby Sass. This better matches the semantics of\n    the selectors in question, and is more efficient. See [issue 2228][].\n\n12. The old-style `:property value` syntax is not supported in the indented\n    syntax. See [issue 2245][].\n\n13. The reference combinator is not supported. See [issue 303][].\n\n14. Universal selector unification is symmetrical. See [issue 2247][].\n\n15. `@extend` doesn't produce an error if it matches but fails to unify. See\n    [issue 2250][].\n\n16. Dart Sass currently only supports UTF-8 documents. We'd like to support\n    more, but Dart currently doesn't support them. See [dart-lang\u002Fsdk#11744][],\n    for example.\n\n[issue 1599]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F1599\n[issue 1126]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F1126\n[issue 2120]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F2120\n[issue 1122]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F1122\n[issue 2176]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F2176\n[issue 2144]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F2144\n[issue 1496]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F1496\n[issue 1525]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F1525\n[issue 1408]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F1408\n[issue 1050]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F1050\n[issue 2228]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F2228\n[issue 2245]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F2245\n[issue 303]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F303\n[issue 2247]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F2247\n[issue 2250]: https:\u002F\u002Fgithub.com\u002Fsass\u002Fsass\u002Fissues\u002F2250\n[dart-lang\u002Fsdk#11744]: https:\u002F\u002Fgithub.com\u002Fdart-lang\u002Fsdk\u002Fissues\u002F11744\n\nDisclaimer: this is not an official Google product.\n","Dart Sass 是一个使用 Dart 语言编写的 Sass CSS 预处理器的参考实现。它提供了强大的 CSS 扩展功能，支持变量、嵌套规则、混合宏等功能，使得编写和维护 CSS 更加高效和有趣。Dart Sass 具有良好的兼容性和性能，可以与多种前端工具链集成，如 npm、Homebrew 和 Docker 等。适用于需要提高 CSS 开发效率的前端项目，特别是那些已经在使用或计划使用 Sass 的项目。","2026-06-11 03:21:25","top_language"]