We're looking for some help maintaining Grunt. Are you interested?

There are a number of specific things the project needs, such as:

• General grunt and grunt-cli maintenance
• Grunt contrib plugin maintenance
• Website / docs maintenance
• Issue triage
• New features (version 1.0? 2.0? The future!)

If you're interested, please reply in this thread. Let us know how you're interested in helping, and we'll figure out where to go from there. Thanks!

UPDATED: Please read the post at the bottom. Contributions and new helpers welcome!

How can we better promote Grunt?

I, along with @sindresorhus and @kahlil, who emailed us recently, have a few ideas.

We should:

• Tweet more consistently.
• Publish regular blog posts highlighting favorite plugins, tutorials, releases, etc.
• Create our own tutorials, screencasts, guides.
• Adjust docs to address community questions or misunderstandings.
• Respond to StackOverflow questions tagged gruntjs.
• Respond to relevant community comments, in general.

What else?

To help promote Grunt let's create a mini-badge developers can put in their README.md to "promote" that the project is using Grunt.

I was thinking about size (same height at least):

With this content:

(Or just "Built with Grunt")

I can't think helpful dynamic content to put there like how the Travis badge works, maybe somebody has suggestions?

Until then it could be a static image that links to http://gruntjs.com/

@cowboy Have you encountered this issue with the Qunit task? creynders/grunt-jasmine-task#4 I'm getting multiple complaints about phantomjs timing out, but all barebones versions they provide me with work on my setup. The jasmine plugin was largely based on your QUnit plugin and calls phantomjs in largely the same fashion, so it puzzles me that I haven't seen any of these issues with your Qunit plugin.

When I run grunt command like this: C:\dem2cz_node_app>grunt.cmd Fatal error: Arguments to path.resolve must be strings.

I immediately get that error. I have grunt-cli of version 0.1.6

My grunt module tree looks like this: [email protected] node_modules\grunt ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ([email protected]) ├── [email protected] ([email protected]) ├── [email protected] ([email protected], [email protected]) ├── [email protected] ([email protected], [email protected]) └── [email protected] ([email protected])

Tested on multiple machines-all of which were running Windows.

When I npm install -g grunt, grunt is not adding a binary to C:\Documents and Settings\apenneba\npm\. The result is that attempts to run grunt in Command Prompt fail with:

'grunt' is not recognized as an internal or external command

System:

I repeated npm install -g grunt, grunt in Command Prompt as well as Git Bash. In either case, grunt fails to add itself to PATH.

Other packages like mocha, jshint, nodeunit, and tap are successfulling adding themselves to PATH.

$ specs node git os
Specs:

specs 0.4
https://github.com/mcandre/specs#readme

npm --version
1.2.17

node --version
v0.10.3

git --version
git version 1.8.0.msysgit.0

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows XP Professional
OS Version:                5.1.2600 Service Pack 3 Build 2600

Hi, I can't install gruntjs.

$ npm install grunt

then error

npm ERR! Error: No compatible version found: underscore.string@'>=2.2.0rc <2.3.0-'
npm ERR! Valid install targets:
npm ERR! ["0.9.2","1.0.0","1.1.3","1.1.4","1.1.5","1.1.6","2.0.0","2.1.0","2.1.1","2.3.0","2.3.1","2.2.0-rc"]

so I fixed package.json dependencies version.

thanks.

In a build system that I currently use, the initialize build command adds commit hooks for the branch. I'm considering porting this over to Grunt as a plugin. After grunt initialized, the lint and qUnit or any other required commands would be run pre-commit.

Before I wrote anything, I thought I'd see if there was any interest in this, or if anyone has put together a plugin for this yet.

I wanted to bring up a watch task scenario that might by useful and not that uncommon.

Currently the watch task allows us to monitor a file, a group of files or a folder for changes for certain type of files and upon change fire a task that is already defined. This is great but I think there is space and a need for improvement.

Lets say we want to use the watch task for things like CoffeScript, Less, Stylus compiling instead of using their own watch features for the purpose of centralizing our tasks and also fill in for the absence of a watch feature like in the case of Less.

At this point when a task is initiated upon a file change we can only run an existing task without really knowing which file has changed. If the name of the file that has changed can be passed to a task that knows how to handle it would be very beneficial.

I'll try to explain with an example:

Lets say we are watching a folder for changes in CoffeScript files. If one file changes, we don't necessarily want to re-compile all the files but just the one that has changed.

Given that currently there is no way for tasks to communicate with one another, enabling such mechanism may even lead to some other useful stuff.

Ultimately I'd like to use grunt for everything that it is or potentially might be able to handle and avoid the need of using other build / minify / compile tools.

Grunt's config file is organized by tasks.
This makes it very difficult to organize. Even if split into separate task files, it's likely that a single feature will span several tasks, and multiple features will overlap tasks.

The concept of Package by feature, not layer would greatly improve the way we organize our Gruntfile configuration.

@cowboy @stevenvachon @k3n @brian-frichette Thoughts?

Right now it's called grunt.js which makes me think it's the actual source of Grunt, which it clearly is not.

• In Rake, we have Rakefile
• In Make, we have Makefile
• In Jake, we have Jakefile
• In Ant: build.xml

Should the configuration file for the project be something other than grunt.js? Perhaps like gruntfile.js or Gruntfile ?

https://github.com/gruntjs/grunt/blob/82d79b803798f2a5f19662df9e12bef977dfa189/.github/workflows/test.yml#L16 https://github.com/gruntjs/grunt/blob/82d79b803798f2a5f19662df9e12bef977dfa189/package.json#L10

Propose doing:

node: [14, 16, 18] 
"node": ">=14.14"

why 14.14 specifically? fs has rm that can replace rimraf

This will use dependabot to update any github action which this project uses.

https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot

Where to start if you are new to GRUNT?

Can you help me start with using GRUNT (or is it a legacy tool???)

Is the documentation up to date?

I am unsure how to start using GRUNT (with VS Code in a TypeScript project) and I do not know if it is still a thing that many people are using or not... I have the impression that it could help me fix many many problems I have at managing my (too many) projects...

I am new to GRUNT and I was looking at the documentation and the version was off compared to the available version on NPM.

At the moment of writing this:

• Stable: v1.4.1 on the web site
• npmjs.com: v1.5.2 on NPM

 It appears that the version was updated only 12 hours ago 🎉

Useless rant to make you smile

I have that same feeling as when you arrive at the party and the best food in the buffet is all gone... I am unsure if I am too late to get into the GRUNT adventure when I read stuff like -> Grunt 0.4.x requires stable Node.js versions >= 0.8.0 or Be advised Grunt 1.0.0 no longer supports Node.js v0.8.

I think I started using nodeJS at v8.x and I have looked up on Wikipedia for insight but the information about older versions only starts at 0.10 (Node.js 0.8.0 was introduced on 2012-06-22).

When I try to run the grunt command I get the following error:

node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'liftoff'
Require stack:
- /usr/share/nodejs/grunt-cli/bin/grunt
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/usr/share/nodejs/grunt-cli/bin/grunt:7:15)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/usr/share/nodejs/grunt-cli/bin/grunt' ]
}

• Node.js: v16.13.0
• NPM: 8.1.0