basedrnc / sbt-closure

sbt-web plugin with Google Closure Compiler integration

sbt-closure

sbt-web plugin which integrates with Google’s Closure Compiler.

Plugin

Add the plugin to your project/plugins.sbt:

addSbtPlugin("net.ground5hark.sbt" % "sbt-closure" % "0.1.4")

Add the Sonatype releases resolver:

resolvers += Resolver.sonatypeRepo("releases")

Enable the sbt-web plugin for your project:

lazy val root = (project in file(".")).enablePlugins(SbtWeb)

Add the closure task to your asset pipeline in your build.sbt:

pipelineStages := Seq(closure)

Configuration options

Option	Description
suffix	Suffix to append to each file compiled by closure. Defaults to ".min.js"
flags	List of command line flags to provide to the closure compiler. Must be in the format of --option-name=value or --option-flag
parentDir	Parent directory name where closure compiled JS will go. Defaults to "closure-compiler"

An example of providing options is below:

Closure.suffix := ".min.js"

Closure.flags := Seq("--formatting=PRETTY_PRINT", "--accept_const_keyword")

This will produce assets with the specified Closure.suffix suffix value under the Closure.parentDir directory within the target folder. This will be target/web/public/main or target/web/stage. For a full list of closure compiler options, see the official documentation page. You can also specify includeFilter in closure or excludeFilter in closure to select files on a custom criteria.

License

This code is licensed under the MIT License.

sbt-closure's Issues

Upgrade to the latest Closure Version

Hello, currently you aren't on the latest closure-compiler version.

--js-output-file not supported

It seems that in the plugin code you are stripping away the most useful feature of the entire compiler, for reasons unknown. How can an app be minified to a single file or a one file per module approach?

Both features are made possible by the compiler with the Google Closure Library and Angular.

0.1.4 is not in sonatype releases repo

https://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22net.ground5hark.sbt%22%20AND%20a%3A%22sbt-closure%22
lists 0.1.0 through 0.1.3.

errors compiling angular-scenario and angular-mocks

Use an alternate target folder

You should probably publish into your own subfolder under the target folder... The asset pipeline will ultimately deliver the files to where they need to be.

https://github.com/ground5hark/sbt-closure/blob/master/src/main/scala/net/ground5hark/sbt/closure/SbtClosure.scala#L70

Test project

You may benefit from a test sub project. Please see sbt-uglify for an example. They help with dev iterations.