Registry / devops / ut-tools

ut-tools

JSON →
library7.13.2jsnpmunverified

ut-tools is a suite of command-line interface (CLI) scripts designed for continuous integration, continuous delivery, and general automation tasks within JavaScript projects. It provides a pre-configured set of utilities for common CI/CD workflows, including generating changelogs (`ut-changelog`), running tests (`ut-test`), checking code coverage (`ut-cover`), linting JavaScript and CSS files (`ut-lint`, `ut-lint-js`, `ut-lint-css`), and automating release processes (`ut-release`, `ut-release-lerna`). Currently at version 7.13.2, the package has shifted its primary installation model since version 7, requiring global installation rather than being added to `devDependencies` to optimize `npm install` performance. It is intended for direct use within `package.json` scripts or as standalone CLI commands, not as a library for programmatic import.

devopstesting
npm install ut-tools
github ↗package ↗
INSTALL
IMPORT
SIG · UT-TOOLS
U
ut-tools
devopsjavascriptv7.13.2
Install
—
Import
—
Disk
—
Pass rate
0/ 6
Env Coverage0 / 6
glibc
18–22
musl
18–22
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18–226 runs
build_error
glibc
node 18–226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

ut-changelog
✓ ut-changelog
✗ import { changelog } from 'ut-tools'
This package primarily exposes CLI commands, not library functions for programmatic import. Use directly in package.json scripts or via npx.
ut-lint
✓ ut-lint
✗ const lint = require('ut-tools/lint');
Invoke ut-lint as a shell command. It's not a JavaScript module to be imported.
ut-release
✓ ut-release
✗ import { release } from 'ut-tools';
Execute ut-release as a command-line utility for managing package versions and publishing.

Demonstrates global installation and usage of ut-tools commands within package.json scripts.

npm install -g ut-tools // Add to your project's package.json scripts // Example: package.json /* { "name": "my-project", "version": "1.0.0", "scripts": { "lint": "ut-lint", "test": "ut-test", "release": "ut-release" } } */ // Then run from your project directory npm run lint
ut-tools --version
Debug
Known issues
breakingSince version 7, ut-tools must be installed globally (`npm install -g ut-tools`) rather than as a `devDependencies` entry. Installing it locally will not provide the expected CLI commands and may slow down `npm install` processes.
fix
Remove `ut-tools` from your `package.json` `devDependencies` and install it globally using `npm install -g ut-tools`.
affects: >=7.0.0
gotchaConfiguring VSCode ESLint to use ut-tools's predefined rules requires specific workspace or user settings. Incorrect paths will result in VSCode not applying the linting rules or reporting errors.
fix
Add the following to your VSCode settings (user or workspace): `"eslint.options": { "overrideConfigFile": "/path/to/global/npm/node_modules/ut-tools/eslint/.eslintrc.js" }, "eslint.nodePath": "/path/to/global/npm/node_modules/ut-tools/node_modules"`. Replace `/path/to/global/npm/node_modules` with your actual global npm modules path (e.g., `npm root -g`).
affects: >=7.0.0
gotchaut-tools is designed as a collection of command-line utilities and is not intended for programmatic `import` or `require()` within JavaScript or TypeScript application code. Attempting to import symbols directly will fail.
fix
Use the provided scripts as CLI commands in your `package.json` or directly from the terminal. For example, `npm run lint` or `ut-lint`.
affects: >=1.0.0
Errors
Common errors & fixes
Error: Command 'ut-lint' not found
The `ut-tools` package was not installed globally, or the global `node_modules` bin directory is not in your system's PATH.
fix
Ensure `ut-tools` is installed globally by running `npm install -g ut-tools`. Verify your system's PATH includes the global npm bin directory.
ESLint: Cannot read config file: '/enter the installation path here/ut-tools/eslint/.eslintrc.js'
The `eslint.options.overrideConfigFile` setting in VSCode uses an incorrect or unresolvable path to the `ut-tools` ESLint configuration.
fix
Find the correct global installation path of `ut-tools` (e.g., `npm root -g`) and update your VSCode settings with the precise path to the `.eslintrc.js` file.
npm install takes a long time, even for small projects.
Prior to v7, `ut-tools` was often listed as a `devDependency`. Since v7, it is designed for global installation, and local installation adds unnecessary overhead.
fix
Remove `ut-tools` from your `devDependencies` in `package.json` and ensure it is installed globally (`npm install -g ut-tools`).
Upgrade
Version history
7.13.2latest on npm
Audit
Dependencies
noderequiredRuntime environment requirement
npmrequiredPackage manager requirement for installation and scripts
Agent activity
23 hits · last 30 days
node
22
Resources
githubhttps://github.com/softwaregroup-bg/ut-tools ↗
packagehttps://www.npmjs.com/package/ut-tools ↗
ut-tools — npm install ut-tools · libregistry