linter: `napi/oxlint2` package won't work when published

[camc314]

Here, we require some code from the parser package, however on user's systems consuming oxlint, these files will not exist.

oxc/napi/oxlint2/src-js/index.js

Lines 12 to 13 in 2401976

	const { TOKEN } = require('../../parser/raw-transfer/lazy-common.js'),
	walkProgram = require('../../parser/generated/lazy/walk.js');

We need to either:

• bundle the code to avoid this issue
• copy the relevant files (build step??)
• something else?

cc @overlookmotel

[overlookmotel]

I planned to fix that by getting ast_tools to generate extra copies of these files (and other files they require in turn) in napi/oxlint2/src-js/generated.

[overlookmotel]

I can hardly bring myself to say it but... I would really like it if we could convert all this code to TypeScript. I think I've finally been infected by the virus.

My only concern is having accurate stack traces and ease of patching generated files while developing. But I suppose we could run the TS as is with --experimental-strip-types while testing?

[camc314]

My only concern is having accurate stack traces and ease of patching generated files while developing. But I suppose we could run the TS as is with --experimental-strip-types while testing?

using --experimental-strip-types breaks our cli argument parsing, as it's hard to tell which args are node, and which are for us

[camc314]

I think we should convert to TS, bundle, but exclude the generated code from being bundled (so it's completly untouched by the compiler)

[camc314]

oops i missed that you assigned this to yourself

this should be fixed by #12527

[camc314]

this should be fixed now