Skip to content

Commit a432364

Browse files
committed
docs: remove left over chars
1 parent 93d83f7 commit a432364

File tree

2 files changed

+7
-1
lines changed

2 files changed

+7
-1
lines changed

docs/guides/getting-started.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,4 +36,10 @@ Configure commitlint to use conventional config
3636
echo "export default { extends: ['@commitlint/config-conventional'] };" > commitlint.config.js
3737
```
3838

39+
> [!WARNING]
40+
> Node v24 changes the way that modules are loaded, and this includes the commitlint config file. If your project does not contain a `package.json`, commitlint may fail to load the config, resulting in a `Please add rules to your commitlint.config.js` error message. This can be fixed by doing either of the following:
41+
>
42+
> - Add a `package.json` file, declaring your project as an ES6 module. This can be done easily by running `npm init es6`.
43+
> - Rename the config file from `commitlint.config.js` to `commitlint.config.mjs`.
44+
3945
Refer to [configuration documentation](/reference/configuration) for more information.

docs/guides/local-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,4 +152,4 @@ No staged files match any of provided globs.
152152
# husky > commit-msg
153153
```
154154
155-
?> Local linting is fine for fast feedback but can easily be tinkered with. To ensure all commits are linted you'll want to check commits on an automated CI Server too. Learn how to in the [CI Setup guide](/guides/ci-setup).
155+
Local linting is fine for fast feedback but can easily be tinkered with. To ensure all commits are linted you'll want to check commits on an automated CI Server too. Learn how to in the [CI Setup guide](/guides/ci-setup).

0 commit comments

Comments
 (0)