I suggest looking at each commit individually for the best diffs. There's an intermediate commit that shows the differences between the original and newly generated .js and d.ts files. The next commit deletes them, since I don't think we want those artifacts checked in?
There shouldn't be any user-affecting changes in this PR. dist/lexer.js ends up being byte-for-byte identical, and types/lexer.d.ts should be semantically identical (verified manually), though with slightly different formatting.
As discussed in https://github.com/guybedford/es-module-lexer/issues/127, this PR converts the WASM JavaScript bridge to TypeScript.
I suggest looking at each commit individually for the best diffs. There's an intermediate commit that shows the differences between the original and newly generated
.js
andd.ts
files. The next commit deletes them, since I don't think we want those artifacts checked in?There shouldn't be any user-affecting changes in this PR.
dist/lexer.js
ends up being byte-for-byte identical, andtypes/lexer.d.ts
should be semantically identical (verified manually), though with slightly different formatting.For the build, I am using swc + chomp to generate the
.js
file as requested in https://github.com/guybedford/es-module-lexer/issues/127#issuecomment-1204629293. It worked great! However, since swc doesn't generate.d.ts
files, I also included a chomptsc
step with the--emitDeclarationOnly
flag. Hopefully this is OK? The two steps can at least run in parallel.Thanks!