chore: allow cjs and mjs info strings

[aduh95]

It seems ESLint folks are not interested in my meta string proposal, I guess the right move would be to move from

```js esm
// ES module
export {};
```

```js cjs
// CJS module
module.exports = {};
```

```js
// Whichever
console.log();
```

to

```mjs
// ES module
export {};
```

```cjs
// CJS module
module.exports = {};
```

```js
// Whichever
console.log();
```

Refs: nodejs/node#37162
Refs: nodejs/node#37311
Refs: eslint/eslint-plugin-markdown#170

---

FWIW, I'd be up to fork the eslint markdown plugin and maintain ourselves support for the meta string instead, but maybe it's not worth the maintenance burden.

[nschonni]

I'm assuming this works with HighlightJS/Prism and that maybe there is a downstream need to update those CSS/JS bundles to support this when building the docs in nodejs/node

[nschonni]

This was the other "metadata" style I was trying to think of before https://prettier.io/blog/2020/11/20/2.2.0.html#align-code-block-language-detection-with-other-popular-tools-9365httpsgithubcomprettierprettierpull9365-by-kachkaevhttpsgithubcomkachkaev

[aduh95]

I'm assuming this works with HighlightJS

Yes, it works with highlight.js (not sure for Prism), so no need to change the nodejs/node doc generation tooling.

[aduh95]

@nodejs/linting Should we land this?

[aduh95]

@Trott Any chance you'll have time to publish this to npm? I don't think I have the permission to do it myself.

[Trott]

Published 2.1.1 which includes this.