Alexandro.Net

Version 1.0.2

@stackline/grunt-cli

The grunt command line interface

Independent maintenance of grunt-cli 1.5.0. Original authors and licenses are retained.

Installation

# Preserve existing imports with an npm alias
npm install grunt-cli@npm:@stackline/grunt-cli@1.0.2
# Or use the scoped package name in your imports
npm install @stackline/grunt-cli@1.0.2

Node.js: >=10. Read the compatibility and maintenance notes before migrating.

Usage and API

@stackline/grunt-cli

The grunt command line interface.

npm version license GitHub repository Docs Reddit community

Documentation | npm | Issues | Repository

Current package version: 1.0.2

Why this package?

@stackline/grunt-cli is the Stackline-maintained distribution of grunt-cli@1.5.0. It is an independent continuation of grunt-cli; original authors and licenses remain credited below.

Compatibility

Item Value
Package @stackline/grunt-cli@1.0.2
API target grunt-cli@1.5.0
Supported Node.js >=10
License MIT
CLI grunt
Runtime dependencies grunt-known-options, interpret, liftup, nopt, v8flags

Installation

npm install @stackline/grunt-cli

Preserve existing imports and plugin resolution with an npm alias:

npm install grunt-cli@npm:@stackline/grunt-cli

Usage and API reference

grunt-cli Build Status: Linux Build Status: Windows

The Grunt command line interface.

Install this globally and you'll have access to the grunt command anywhere on your system.

npm install -g @stackline/grunt-cli

Note: The job of the grunt command is to load and run the version of Grunt you have installed locally to your project, irrespective of its version. Starting with Grunt v0.4, you should never install Grunt itself globally. For more information about why, please read this.

See the Getting Started guide for more information.

Shell tab auto-completion

To enable tab auto-completion for Grunt, add one of the following lines to your ~/.bashrc or ~/.zshrc file.

# Bash, ~/.bashrc
eval "$(grunt --completion=bash)"

# Zsh, ~/.zshrc
eval "$(grunt --completion=zsh)"

Installing grunt-cli locally

If you prefer the idiomatic Node.js method to get started with a project (npm install && npm test) then install grunt-cli locally with npm install @stackline/grunt-cli --save-dev. Then add a script to your package.json to run the associated grunt command: "scripts": { "test": "grunt test" } . Now npm test will use the locally installed ./node_modules/.bin/grunt executable to run your Grunt commands.

To read more about npm scripts, please visit the npm docs: https://docs.npmjs.com/misc/scripts.

Credits and original authors

Original copyright, license notices and contributor acknowledgements remain part of this distribution. Stackline maintenance does not replace authorship of the original work.

License

MIT. See the license and notice files in the repository.

Community and Links

Use this repository's issue tracker for reproducible bugs and feature requests. Join r/Stackline for examples, usage questions and release discussions.

Upstream issues and maintenance review

Upstream review

Based on grunt-cli@1.5.0, commit 8c791efc931fa8cf80cc98d09d3e20c36501fc0f. All published upstream runtime files match this commit byte-for-byte; npm tarball integrity was independently checked.

The fork preserves runtime files, exports, CLI names and engine declarations. Original license and authorship notices remain. Development tooling runs on Node24 without raising the package runtime requirement.

Issue triage (2026-09-29)

No upstream maintainers were contacted. These are scoped compatibility decisions, not blanket claims that upstream issues are fixed.

Verification

npm ci --ignore-scripts, npm test, npm run test:package, and npm audit --audit-level=low. CI and CodeQL gate the exact immutable package artifact. Packed consumer tests install the resulting archive before exercising its public behavior.

Release changes

Stackline changes

1.0.0

Release files and references

Package bytes, npm provenance and the immutable GitHub release were verified for this version. Security checks describe the reviewed release; documented compatibility risks and upstream reports are not blanket claims of resolution.