https://github.com/sbt/sbt-jshint

Allows jslint to be used from within sbt. Builds on com.typesafe:webdriver in order to execute jslint.js along with the scripts to verify
https://github.com/sbt/sbt-jshint

Last synced: 2 months ago
JSON representation

Allows jslint to be used from within sbt. Builds on com.typesafe:webdriver in order to execute jslint.js along with the scripts to verify

• Host: GitHub
• URL: https://github.com/sbt/sbt-jshint
• Owner: sbt
• License: other
• Fork: true (jroper/sbt-jshint-plugin)
• Created: 2013-10-29T01:37:43.000Z (about 11 years ago)
• Default Branch: main
• Last Pushed: 2024-10-16T09:42:53.000Z (3 months ago)
• Last Synced: 2024-10-18T05:59:36.686Z (3 months ago)
• Language: Scala
• Size: 520 KB
• Stars: 21
• Watchers: 8
• Forks: 20
• Open Issues: 8
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-sbt-plugins - sbt-jshint

README

        
sbt-jshint

==========

[![Build Status](https://github.com/sbt/sbt-jshint/actions/workflows/build-test.yml/badge.svg)](https://github.com/sbt/sbt-jshint/actions/workflows/build-test.yml)

Allows JSHint to be used from within sbt. Builds on com.github.sbt-js-engine in order to execute jshint.js

along with the scripts to verify. js-engine enables high performance linting given parallelism and native JS engine execution.

To use this plugin use the `addSbtPlugin` command within your project's `plugins.sbt` (or as a global setting) i.e.:

    addSbtPlugin("com.github.sbt" % "sbt-jshint" % "2.0.0")

Your project's build file also needs to enable sbt-web plugins. For example with build.sbt:

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

By default linting occurs as part of your project's `jshint` task. Both src/main/assets/\*\*/\*.js and

src/test/assets/\*\*/\*.js sources are linted.

Options can be specified in accordance with the

[JSHint website](http://www.jshint.com/docs) and they share the same set of defaults. To set an option you can

provide a `.jshintrc` file within your project's base directory. If there is no such file then a `.jshintrc` file will

be search for in your home directory. This behaviour can be overridden by using a `JshintKeys.config` setting for the plugin.

`JshintKeys.config` is used to specify the location of a configuration file.