Armano

i have few news about this issue, and this seem to be caused by our normalization of paths

i do agree with createing documentation for this, there is already few projects that use ts-estree directly (eg. prettier)

are we planning to add description fields to schema of rules, for describing specific options? https://deploy-preview-5386--typescript-eslint.netlify.app/rules/explicit-function-return-type#options https://json-schema.org/draft/2020-12/json-schema-core.html#name-schema-vocabularies 

alt should be present on logo and we should include [`aria-hidden`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-hidden) to

> @elliotleelewis thanks for the info. > Someone just mentioned that [the babel preset ist still targeting node v6](https://github.com/conventional-changelog/commitlint/blob/master/%40packages/babel-preset-commitlint/index.js#L30). > Might be good to clean this up. Instead of targeting...

> Ah thanks for pointing this out. I think this creates two bodies of work for us: > > 1. resolve from the current config file for plugin paths starting...

Currently there is a way to load local plugins by simply require'ing it ```js // commitlint.config.js { plugins: [require('./dir/my-custom-plugin.js')], } ```

yes, its same package as eslint is currently using https://github.com/eslint/eslint/blob/75fea9bcdd3dde5a07e0089d9011a4df518cdbe3/package.json#L51

i updated proposal a little, to make it more clear

json schema, based on [SchemaStore/schemastore#1443](https://github.com/SchemaStore/schemastore/pull/1443) https://json.schemastore.org/commitlintrc