The repo description says "A JS/TS Engine". What are your plans on integrating/implementing TypeScript? Also I see the codebase is in Rust but there's some setup/tooling for Go. Are you planning to release it as a Go package?
Oh, the first question is answered in the post:
> Yavashark’s CLI can run React with TypeScript
Nice, curious to see how that works internally - is it type stripping? I wonder about source mapping, for example, line numbers in error messages.
Well, yes to both. The initial reason why I started the engine because I wanted something that could run typescript natively. For now it just does type-stripping and some transformations to run react code.
For source mapping, some errors are converted, mainly syntax ones, but there are no real conversions for errors arbitrarly thrown in the engine.
The tooling, mostely no. But if people want it I don't see any issue why I should not do that.
Congrats on the public launch!
The repo description says "A JS/TS Engine". What are your plans on integrating/implementing TypeScript? Also I see the codebase is in Rust but there's some setup/tooling for Go. Are you planning to release it as a Go package?
Oh, the first question is answered in the post:
> Yavashark’s CLI can run React with TypeScript
Nice, curious to see how that works internally - is it type stripping? I wonder about source mapping, for example, line numbers in error messages.
Well, yes to both. The initial reason why I started the engine because I wanted something that could run typescript natively. For now it just does type-stripping and some transformations to run react code. For source mapping, some errors are converted, mainly syntax ones, but there are no real conversions for errors arbitrarly thrown in the engine.
The tooling, mostely no. But if people want it I don't see any issue why I should not do that.