fix: fix code display in release blog

[Trott]

Fixes: #3976

[targos]

The problem will come back next time we put an mjs code block in release notes. Node's linter forbids ESM syntax in js blocks

[Trott]

The problem will come back next time we put an mjs code block in release notes. Node's linter forbids ESM syntax in js blocks

Best option is probably to add mjs and cjs options for code highlighting in this repo. What do you think, @aduh95?

Refs: nodejs/node#37162

We probably don't need anything as elaborate as what's in the docs (with a toggle switch and all that). We probably just need to map mjs and cjs to js in the highlighter somehow, or else add something in our build process that converts mjs and cjs code fences to js code fences.

[richardlau]

If it's just the release posts we already remap console in

nodejs.org/scripts/release-post.js

Lines 107 to 113 in a654c6b

	// Make sure that all the console has been replaced
	// by "```shell-session" for metalsmith-prism's check to pass
	const rxSectionConsole = /```console/igm
	const matches = rxSectionBody.exec(section)
	return matches
	? matches[1].trim().replace(rxSectionConsole, '```shell-session')
	: Promise.reject(new Error(`Could not find changelog body of ${version} release`))

[aduh95]

I think we need to do the same thing I did in nodejs/node#37311.

[Trott]

I think we need to do the same thing I did in nodejs/node#37311.

If I understand correctly, that would fix lint errors but not the display error that we saw here.

[aduh95]

Hum indeed, I misread the issue. It looks like a bug in Prism:

Failed to load prism syntax: mjs
Error: Cannot find module 'prismjs/components/prism-mjs.js'

I'm able to workaround the issue by adding these lines at the top of build.js:

const { languages } = require('prismjs');
languages.mjs = languages.js;

[nschonni]

I wonder if maybe the "preLoad" option is also applicable https://www.npmjs.com/package/metalsmith-prism#preload-optional