Show more info in missing customSyntax warning

[hudochenkov]

Which issue, if any, is this issue related to?

#5604 (comment)

Is there anything in the PR that needs further explanation?

Now message included file path to understand what file causes the warning. And suggest known syntax to previously inferred extensions.

Before:

When linting something other than CSS, you should install an appropriate syntax, e.g. postcss-scss, and use the "customSyntax" option

After:

/Users/person/projects/styles.tsx: When linting something other than CSS, you should install an appropriate syntax, e.g. "@stylelint/postcss-css-in-js", and use the "customSyntax" option

[jeddy3]

The message is much better, thanks!

I've requested one small change.

[jeddy3]

Suggested change

	md: '@stylelint/postcss-markdown',
	md: 'postcss-markdown',

We're going to deprecate our fork in favour of the original package. It works fine. It just needs someone to take ownership and update the dependencies at some point.

@stylelint/postcss-css-in-js is the special case as quite a bit of work was done to it since it was forked from the original package, so our fork will need to stick around a while until we can deprecate it (see https://github.com/stylelint/postcss-css-in-js/issues/225)

[hudochenkov]

Done!

[jeddy3]

Thanks!

[ybiquitous]

LGTM 👍🏼