doc: add initial doc on how to update cjs-module-lexer

[mhdawson]

Add some initial doc based on discussion with Guy
Bedford.

Signed-off-by: Michael Dawson [email protected]

[nodejs-github-bot]

Review requested:

• @nodejs/tsc

[mhdawson]

@guybedford I think this reflects what I understood from our discusison last week. Could you take a look to confirm?

[richardlau]

There's a link in the ESM docs that is supposed to be updated to match the version of the lexer being used:

node/doc/api/esm.md

Line 1544 in 895cc57

<!-- Note: The cjs-module-lexer link should be kept in-sync with the deps version -->

[mhdawson]

@richardlau thanks, added that as a step.

[aduh95]

Instead of documentation, I wonder if it wouldn't be more worth to add an automation.

[mhdawson]

Instead of documentation, I wonder if it wouldn't be more worth to add an automation.

@aduh95, I think automation is always good, but even if that existed, some doc that points to the automation which could then be the doocument for the specific steps still makes sense. I know I ran across some scripts in the repo that help to build some of the other dependencies but only ran across them by accident. Long way of saying that I think we need an entry point doc for each dependency to make other parts discoverable. If we had automation for everything and there was nothing else to say/explain then we might be able to consolidate into fewer docs.

[guybedford]

Thanks for digging into this Michael.

As mentioned, at some point it may be worthwhile to run a recent Wasm build with fixed versions of the toolchain, note those toolchain versions and update the Wasm binary.

The project is very much in a maintenance mode and will only be getting bug fixes and not feature development going forward.

[mhdawson]

@aduh95 accepted all of your suggestions

[mhdawson]

Landed in cc82f6f