chore(ci): add "publish" GHA

[JakobJingleheimer]

Todo:

• Set up repo secret for codemod
• Each recipe being published needs to be bundled and then sent to the codemod registry. Thereafter, the bundle generated by CI can be discarded.

Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.

Files not reviewed (1)

• package.json: Language not supported

Comments suppressed due to low confidence (1)

.github/workflows/publish.yml:40

• The node-version value 'node' is ambiguous. It should be a specific version number or range, like '14' or '14.x'.

node-version: node

[AugustinMauroy]

LGTM !

[JakobJingleheimer]

There are a few issues blocking this:

• bundling via esbuild encounters a platform-specific node addon used by ast-grep, which can't be bundled
  • codemod publish doesn't have a programmatic API, so it'll need leverage spawn
• codemod publish can handle the bundling but doesn't support distributed config, and the bundle it builds errors (transformer cannot be null)
  • there's not much documentation around what it's doing (they're working on it)

[JakobJingleheimer]

• the bundle it builds errors (transformer cannot be null)

This turned out to be a red-herring: it was actually throwing when it got to module.register('@nodejs-loaders', import.meta.url) because when codemod publish builds the bundle (also via esbuild), esbuild does not realise there is a dependency it needs to include. evanw/esbuild#4016

[AugustinMauroy]

Suggested change

	const opts: BuildOptions = {
	format: 'esm',
	};
	export default opts;
	export default {
	format: 'esm',
	} as BuildOptions;