A Maven plugin that allows to compile SASS using Dart Sass
<build>
...
<plugins>
<plugin>
<groupId>io.github.cleydyr</groupId>
<artifactId>dart-sass-maven-plugin</artifactId>
<version>1.3.0</version>
<executions>
<execution>
<id>generate-css-using-sass</id>
<phase>generate-resources</phase>
<goals>
<goal>compile-sass</goal>
</goals>
</execution>
</executions>
</plugin>
...
</plugins>
</build>Dart Sass Maven Plugin will run on any operating systems and architectures available on the Dart Sass releases page. As of now, they are:
| Linux | Mac | Windows | Linux (musl) | |
|---|---|---|---|---|
| ia32 | ✅ | ❌ | ✅ | ✅ |
| x64 | ✅ | ✅ | ✅ | ✅ |
| arm64 | ✅ | ✅ | ❌ | ✅ |
| arm | ✅ | ❌ | ❌ | ✅ |
The Dart Sass Maven Plugin will automatically detect the operating system and architecture of the machine where it's running. If it fails to do so, it will fall back to the following defaults:
- Architecture:
ia32 - Operating system:
linux
Dart Sass Maven Plugin will determine the latest Dart Sass version available on the Dart Sass releases page if the parameter is not set. As a fallback, if the artifacts for a given OS/arch are unavailable, it will use the latest version available for the same OS/arch combination (available on GitHub or cached in the local file system, if possible).
Warning
It's recommended to use a fixed version parameter value in your project to help achieve a reproducible build and avoid errors caused by GitHub temporarily blocking the client's IP when the plugin checks for the latest version multiple times from the same IP. That may happen in an automated CI environment with frequent builds for example.
This plugin included all released archives for a given Dart Sass version in previous versions. However, starting from version 1.0.0, this plugin will download the latest release of Dart Sass if it's not found in the temporary folder or in the cached files' directory. Should this plugin be used in an air-capped environment, you should provide a release archive inside the cached files directory and at least pin the Dart Sass' release version with the <version> parameter. The release archive should be a file named release on the subpath <os>/<arch>/<version>/ inside the cached files' directory.
This plugin will detect Maven's proxy configurations and use it if necessary to download a release artifact and query GitHub to discover the latest Dart Sass release.
This goal compiles a set of sass/scss files from an input directory to an output directory.
Full name: io.github.cleydyr:dart-sass-maven-plugin:0.4.0:compile-sass
Binds by default to the lifecycle phase: process-resources.
<arch>
This parameter represents the Dart Sass architecture that should be used to compile Sass files. If left unset, it will be autodetected by the plugin. Accepted values are "x64", "aarch32", "aarch64" and "ia32".
Type: String
Required: No
<os>
This parameter represents the Dart Sass operating system that should be used to compile Sass files. If left unset, it will be autodetected by the plugin. Accepted values are "linux", "linux-musl", "macos" and "windows".
Type: String
Required: No
<version>
This parameter represents the Dart Sass version that should be used to compile Sass files. If left unset, the version available at https://github.com/sass/dart-sass/releases/latest will be used.
Type: String
Required: No
<cachedFilesDirectory>
This parameter represents a path in the local file system where the release archive downloaded from the internet will be stored. If left unset, it will default to
- $HOME/.cache/dart-sass-maven-plugin/ on *nix operating systems; or
- %LOCALAPPDATA%\dart-sass-maven-plugin\Cache on Windows operating systems.
Type: java.io.File
Required: No
<color>
This flag tells Sass to emit terminal colors. By default, it will emit colors if it looks like it's running on a terminal supporting them. Set it to false to tell Sass to not emit colors.
Type: boolean
Required: No
Default: true
<embedSourceMap>
This flag tells Sass to embed the contents of the source map file in the generated CSS, rather than create a separate file and link to it from the CSS.
Type: boolean
Required: No
Default: false
<embedSources>
This flag tells Sass to embed all the contents of the Sass files that contributed to the generated CSS in the source map. This may produce very large source maps, but it guarantees that the source will be available on any computer no matter how the CSS is served.
Type: boolean
Required: No
Default: false
<errorCSS>
This flag tells Sass whether to emit a CSS file when an error occurs during compilation. This CSS file describes the error in a comment and in the content property of body::before so that you can see the error message in the browser without switching back to the terminal.
By default, error CSS is enabled if you're compiling to at least one file on disk (as opposed to standard output). You can activate errorCSS explicitly to enable it even when compiling to standard out (not supported by this Maven plugin) or set it explicitly to false to disable it everywhere. When it's disabled, the update flag and watch flag (the latter being not yet supported by this Maven plugin) will delete CSS files instead when an error occurs.
Type: boolean
Required: No
Default: true
<inputFolder>
Path to the folder where the sass/scss are located.
Type: java.io.File
Required: No
Default: src/main/sass
<loadPaths>
Paths from where additional load path for Sass to look for stylesheets will be loaded. It can be passed multiple times to provide multiple load paths. Earlier load paths will take precedence over later ones.
Type: java.util.List
Required: No
<noCharset>
This flag tells Sass never to emit a @charset declaration or a UTF-8 byte-order mark. By default, or if the charset flag is activated, Sass will insert either a @charset declaration (in expanded output mode) or a byte-order mark (in compressed output mode) if the stylesheet contains any non-ASCII characters.
Type: boolean
Required: No
Default: false
<noSourceMap>
Sass won't generate any source maps if the noSourceMap flag is set. If explicitly set, it will void other source map options (namely sourceMapURLs, embedSources, and embedSourceMap).
Type: boolean
Required: No
Default: false
<noUnicode>
This flag tells Sass only to emit ASCII characters to the terminal as part of error messages. By default, Sass will emit non-ASCII characters for these messages. This flag does not affect the CSS output.
Type: boolean
Required: No
Default: false
<outputFolder>
Path to the folder where the CSS and source map files will be created.
Type: java.io.File
Required: No
User Property: project.build.directory
<quiet>
This flag tells Sass not to emit any warnings when compiling. By default, Sass emits warnings when deprecated features are used or when the @warn rule is encountered. It also silences the @debug rule. Enabling it will also silence output when in watch mode.
Type: boolean
Required: No
Default: false
<quietDeps>
This flag tells Sass not to emit deprecation warnings that come from dependencies. It considers any file that's transitively imported through a load path to be a "dependency." This flag doesn't affect the @warn rule or the @debug rule.
Type: boolean
Required: No
Default: false
<sourceMapURLs>
This option controls how the source maps Sass generates link back to the Sass files that contributed to the generated CSS. Dart Sass supports two types of URLs:
RELATIVE(the default) uses relative URLs from the location of the source map file to the locations of the Sass source file; andABSOLUTEuses the absolute file: URLs of the Sass source files. Note that absolute URLs will only work on the same computer where the CSS was compiled.
Use either RELATIVE or ABSOLUTE in the plugin configuration.
Type: com.github.cleydyr.dart.command.enums.
SourceMapURLs
Required: No
Default: RELATIVE
<stopOnError>
This flag tells Sass to stop compiling immediately when an error is detected rather than trying to compile other Sass files that may not contain errors. It's mostly useful in many-to-many mode (which is the mode currently supported by this Maven plugin).
Type: boolean
Required: No
Default: false
<style>
This option controls the output style of the resulting CSS. Dart Sass supports two output styles:
EXPANDED(the default), which writes each selector and declaration on its own line; andCOMPRESSED, which removes as many extra characters as possible and writes the entire stylesheet on a single line.
Use either EXPANDED or COMPRESSED in the plugin configuration.
Type: com.github.cleydyr.dart.command.enums.Style
Required: No
Default: EXPANDED
<trace>
This flag tells Sass to print the full Dart stack trace when encountering an error. It's used by the Sass team for debugging errors.
Type: boolean
Required: No
Default: false
<update>
If this flag is set to true, Sass will only compile stylesheets whose dependencies have been modified more recently than the corresponding CSS file was generated. It will also print status messages when updating stylesheets.
Type: boolean
Required: No
Default: false
This goal compiles a set of sass/scss files from an input directory to an output directory and keeps the process open watching for changes in the source files. A message will be written to the standard output each time a source file changes.
Full name: io.github.cleydyr:dart-sass-maven-plugin:0.4.0:watch-sass
By default, it binds to no lifecycle phase.
In addition to the parameters that are available to the compile-sass goal, the following parameter is also available:
<poll>
This flag tells Sass to manually check for changes to the source files every so often instead of relying on the operating system to notify it when something changes. This may be necessary if you’re editing Sass on a remote drive where the operating system’s notification system doesn't work.
Type: boolean
Required: No
Default: false
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent