commit-m | Web service for search commit message examples | Web Framework library

I was facing the same issue which is why I stumbled across this post.

My issue was I was using the wrong node version. I faced a similar issue after upgrading to Angular 13 but I was using node version v14.2.0.

I changed the node version to v14.15.0 and it worked.

nvm use v14.15.0

PS: NVM manages multiple nodejs versions.

You got the following error message:

The text

With xmlstarlet:

While you can use --if and --else for xmlstarlet sel (see https://stackoverflow.com/a/35671038/2703456 for example), I don't think you can use them for xmlstarlet ed. I hardly ever use xmlstarlet, so I'm not entirely sure.
That means you'll have to do it in Bash...

The coreutils repository sets up Git hooks in your local clone of the repository. You can find the commit message check in scripts/git-hooks/commit-msg.

It is run every time you try to commit. It defines the allowed keywords starting in line 14:

There is no merge.commit option: see the source code, where you can see which options are handled, and observe the lack of a merge.commit option. There was no such option in 2014 either (clone and inspect the Git source to verify this, if you like).

The merge.ff option has been around since then, but merge.commit has, as far as I can tell, never existed. You can of course run a command other than git merge to start merging, and by doing that, you can make this command supply --no-commit as an explicit argument. Note, however, that you cannot alias Git built-ins, so there is no way to make a Git alias that inserts --no-commit when you run git merge. Run git mymerge and make that a Git alias, or run mymerge and make that a shell alias, but do not run git merge.

(Your other option is of course to set branch.name.mergeoptions for every branch name.)

The best way to handle this is indeed to use the prepare-commit-msg hook. When you create one, you should take note of the arguments passed to it, and, unless you want to make your life needlessly difficult, avoid modifying it when you're using git commit --amend (such as when the second argument is commit).

Note that the hook needs to modify the file that's the first argument in place, which is different from what many people expect. As such, you will often want to use something like the -i argument to Perl, Ruby, or sed, or a scriptable line editor like ed -s or ex -s with the w command.

If you're trying to add a trailer, then git interpret-trailers may be helpful to add the entry you desire based on the config, and you can customize it to not add an entry if one is already present. It can't use user.team, but it can use other configuration options to set the trailer.

An example where you're trying to simply replace a %(team) token from the template with the value of user.team looks like this:

Don't use aliases. They are in every aspect inferior to functions.

Writing this as a function also avoids the quoting errors you probably were bumping into when trying to create an alias (though it's not impossible to solve those, too; but if that's what you want, probably ask a new question with your actual attempt).

The following only has very small changes compared to your original (and to the extent that the original worked in the first place, it would have worked just as well without any changes at all).

I've suggested "**/*.{js,vue}": ["npm run lint:js:fix"], first of, lint:js:fix is subjective and up to you. This is what Kent C Dodds is using, so I'm just naming it in the same way.

But you could totally have lint:watermelon-potato-hehe instead, doesn't matter.

Now, about your propositions:

1. "**/*.{vue,js,jsx,ts,tsx}": "npm run lint", this one is targeting more extensions, which is totally fine. You may not really use .tsx/.jsx since it's not really popular among Vue devs.
   About .ts itself, it may probably work good enough (maybe you'll need to add some plugins to your ESlint configuration). I'm not into TS so I can't really help on this one but it's out of the husky/lint-staged scope anyway.
   Last time I started a Vue3 project, I've used Vitesse which has some nice defaults with TS, this may be a good start for you maybe.

As for the second part, since I like to setup my own ESlint config, with some simple and well documented API, we're using eslint --ext .js,.vue --fix. That way I'm sure of what is happening and how to troubleshoot it if needed.
vue-cli-service lint may be a good default package aimed towards Vue with some defaults, I'm not sure what's inside it and even if it's probably just an ESlint with some baked-in configuration, again we prefer to make our own Vue configuration with vanilla ESlint.

So yeah, if you need to go fast, use vue-cli-service lint for some quick linting, if you want to have a better flow in your project and want to fine grain your config, use vanilla ESlint, you'll get less trouble overall IMO.

1. "**/*.{vue,js,jsx,ts,tsx}": "eslint --ext .vue,.js,.jsx,.ts,.tsx --fix". On the right side, we globally have the same lint:js:fix scripts but with additional extensions.

So, you may ask why are we even writing the extensions on the left side for lint-staged and on the right side for lint:js:fix? I'd answer that those are not really needed on the right side (AFAIK), because lint-staged will only run the command to the left list of extensions.
Here, we wanted to be more explicit about the exact extensions we're targeting and also, it enables you to run npm run lint:js:fix in your CLI at any given point without getting errors on files ESlint is not handling (.txt, .json, .md, .jpg etc...).
So it could maybe be removed (not sure), fastest way to be sure is to try!

1. "**/*.{vue,js,jsx,ts,tsx}": "eslint --fix", this one may work fine as explained in the previous paragraph. Didn't tried it myself thought.

Regarding .html, you should not have a lot of those in your Vue project. You could use the W3C validator to check for any errors if you really need it.
If you're speaking about your HTML in the template tags in your .vue files, those will be ESlint'ed properly. If you setup a Prettier on top of it, you will also get some nice auto-formatting which is really awesome to work with (once your team has agreed on a .prettierrc config).

Regarding .json files, those are not handled by ESlint. ESlint is only for JavaScript-ish files. If you want to lint/format your .json or even any other extensions at all, you can aim towards NPM, find a package that suits your team's needs and add it to your chain like "**/*.json": ["npm run lint-my-json-please"] and you should be good!

At the end, husky + lint-staged are not doing anything special really. They are tools to automate what you could write yourself in a CLI, so if it's working when done manually and you're happy with the result, you can put it in your config but you need to first found what the proper package and it's configuration.

In your package.json, you could have the following