v2 rewrite

[Floffah]

So, ever since I started this project I've wanted to rewrite the plugin to use a custom parser (or that of something like a faster babel alternative) to create type definitions without typescript in watch mode and use typescript at the end (or use it configurably for both) just because of how slow typescript is

If I was going to use a custom parser I would use Nearley and Moo

I want some feedback before I start this. Does anyone know of a good typescript parser that is faster than typescript (or is using typescript just for its parser but is fast?). If there isnt a good one, is Nearley fast enough (from my experience it is)

[Floffah]

since creating this i made the process a lot faster but i feel like this is still something i could do to make it as fast as esbuild

[ckissane]

That would be great, and though I don't have suggestions for implementation details off the top of my head
looking at:

• https://www.npmjs.com/package/@typescript-eslint/parser
• https://github.com/KFlash/seafox
• https://github.com/microsoft/TypeScript/wiki/Using-the-Compiler-API#getting-the-dts-from-a-javascript-file
  Might be a good start

[Floffah]

ill have a read, thank you

[TomCaserta]

If you output a bundle and package up your source code I believe you can just create d.ts files which comprise of the following:

export * from '../src/index.ts';

As an example. Not sure if you get obscure problems with this but I've been using this to avoid the problem entirely and seems to work so far had no problems with VSCode and the likes.

[Floffah]

this is definitely an option i could add but i feel like not everyone would use it since it more than doubles the package size