modern, maintainable, modular developer tooling for FT.com projects
With Tool Kit [already set up](https://github.com/financial-times/dotcom-tool-kit#installing-tool-kit), install this plugin as a dev dependency:
With Tool Kit [already set up](https://github.com/financial-times/dotcom-tool-kit#installing-and-using-tool-kit), install this plugin as a dev dependency:
With Tool Kit [already set up](https://github.com/financial-times/dotcom-tool-kit#installing-and-using-tool-kit), install this plugin as a dev dependency:
With Tool Kit [already set up](https://github.com/financial-times/dotcom-tool-kit#installing-and-using-tool-kit), install this plugin as a dev dependency:
This plugin manages Tool Kit commands that are run from CircleCI workflows, via a Tool Kit [`Hook`](#hooks) that automatically manages `.circleci/config.yml`. It also exposes state from the CircleCI environment for other plugins to consume generically.
This plugin is for managing Tool Kit hooks that are run from npm scripts (such as `npm run test`).
A plugin that will add CircleCI jobs that will interact with deployment services, such as AWS or Serverless, to your CircleCI config.
Types and functions for an errors-as-first-class-values pattern
A plugin to run [eslint](https://eslint.org/) in your JavaScript code. This plugin uses the ESLint Node.js [API](https://eslint.org/docs/latest/developer-guide/nodejs-api) to run ESLint. It loads the ESLint configuration files (.eslintrc.* files) in your
A bootstrap plugin that provides the minimum required Tool Kit plugins for a "component" (aka an [npm module](https://github.com/Financial-Times/next/wiki/Naming-Conventions#npm-modules)). The plugins are:
Run your Node application.
A bootstrap plugin that provides the minimum required Tool Kit plugins for a containerised application that's deployed to Amazon Elastic Container Service (ECS).
Tool Kit plugin to run [Webpack](https://webpack.js.org)
Tool Kit plugin to format your source code with [Prettier](https://prettier.io).
This plugin manages Tool Kit commands that are run from npm scripts, via a Tool Kit [`Hook`](#hooks) that automatically manages `package.json`.
This plugin is for managing the `publish:tag` hook that is run from circleci to publish the built package to the npm registry.
Tool Kit plugin to run [Mocha](http://mochajs.org)
A plugin to add git hooks to your project via [husky](https://typicode.github.io/husky/#/). These hooks can be configured with different tasks as your project requires.
A plugin to run the [lint-staged](https://github.com/okonet/lint-staged) tool to run linters on files staged via git.
A plugin to run [Jest](https://jestjs.io/) tests. This plugin uses [jest-cli](https://www.npmjs.com/package/jest-cli) to run the tests. You can configure this plugin by specifying the path to the Jest config path.
A bootstrap plugin that provides the minimum required Tool Kit plugins for a "backend" (aka an [API](https://github.com/Financial-Times/next/wiki/Naming-Conventions#apis)) that is deployed to AWS. The plugins are:
A plugin to run [Babel](https://babeljs.io/) to compile ES2015+ syntax.
A plugin to run smoke tests as part of your CircleCI workflow using the [n-test](https://github.com/Financial-Times/n-test) package.