It seems like there was an issue running npx husky add .husky/commit-msg 'npx --no-install commitlint --edit $1' because the command part was more than one word. A workaround I found was to split it up into two parts.

1 - Call npx husky add .husky/commit-msg

This created an empty/ default file in the right place with the following content:

#!/bin/sh
. "$(dirname "$0")/_/husky.sh"

undefined

2 - Then I just replaced undefined with npx --no-install commitlint --edit $1 and it works

This part of the commitlint docs helped me understand that doing it that way was okay

Hope this helps anyone else who encounters the same issue!

alexandreafa,

I got the same issue with yours, package.json file and .git directory are not at the same level. But I found a way to fix it, Step by step.

• Install commitlint (ref:https://github.com/conventional-changelog/commitlint)

# Install commitlint cli and conventional config
npm install --save-dev @commitlint/{config-conventional,cli}
# For Windows:
npm install --save-dev @commitlint/config-conventional @commitlint/cli

# Configure commitlint to use conventional config
echo "module.exports = {extends: ['@commitlint/config-conventional']}" > commitlint.config.js  

# Add hook
cat <<EEE > .husky/commit-msg
#!/bin/sh
. "\$(dirname "\$0")/_/husky.sh"

npx --no -- commitlint --edit "\${1}"
EEE   

chmod a+x .husky/commit-msg

• update the commit-msg

CHANGE
npx --no -- commitlint --edit "\${1} 

TO
cd nestedFolderRoot npx --no -- commitlint --edit "\${1} 

fixed.

Now you could use git commit -m "type: xxxx" to commit it.

The only workaround for this is to rename the pre-commit file to commit-msg. This tells the husky to run the script on the current commit message.

Also, I've reported this as a bug on Commitlint GitHub issues.

Install Husky

1. Run npm i husky --save-dev
2. Run npx husky init

The init command simplifies setting up husky in a project. It creates a pre-commit script in .husky/ and updates the prepare script in package.json. Modifications can be made later to suit your workflow. Husky doc

Install commitlint

3. Run npm i @commitlint/cli @commitlint/config-conventional --save-dev
4. Create a commitlint.config.js file at the root of the project.

module.exports = {
  extends: ['@commitlint/config-conventional'],
};

5. in the .husky folder, add commit-msg file

npx --no-install commitlint --edit "$1"

6. (optional) remove the pre-commit file if you do not have any test

Test it

7. Just commit something, ex: git commit -m "Keep calm and commit"

ENOENT: no such file .../COMMIT_EDITMSG ?

Just open the .git folder and add an empty COMMIT_EDITMSG file.
Git needs it to know the title you're trying to type, maybe he doesn't have the access to create the file.