Forking the typescript compiler and building on it?

• ttypescript

  9 1,520 3.5 TypeScript

  Over TypeScript tool to use custom transformers in the tsconfig.json

There is also a forked version of the compiler that allows custom transformers: https://github.com/cevek/ttypescript

• TypeScript

  1,305 98,060 9.9 TypeScript

  TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  

And Typescript's compiler API but I don't think it's exactly what you'd want. But i've never looked at it so idk. https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• TypeScriptToLua

  10 1,968 8.3 TypeScript

  Typescript to lua transpiler. https://typescripttolua.github.io/

  

It might be helpful to keep in mind: Typescript is a compiler that parses a Typescript AST and prints out whatever you want. So if your goal is to use it in a JS context, the only thing regulating what you do with it is that it outputs valid JS that can be interpreted by the various JS engines. There are projects like TypeScriptToLua which uses the TS compiler to print out Lua code.

• simple-ts-transform

  1 9 0.0 TypeScript

  Library to help create simple typescript transformers

  

My point is, instead of *forking* Typescript, why not just write a transform? Instead of creating new syntax, write up a visitor that will walk through something that looks like a result type and output the JS code that handles it correctly. This is how things like optional chaining were supported before they were incorporated into the compiler. Here's a similar question from a few weeks ago that I responded to in more detail.

• ts-optchain

  1 585 0.9 TypeScript

  Discontinued Optional Chaining for TypeScript

  

My point is, instead of *forking* Typescript, why not just write a transform? Instead of creating new syntax, write up a visitor that will walk through something that looks like a result type and output the JS code that handles it correctly. This is how things like optional chaining were supported before they were incorporated into the compiler. Here's a similar question from a few weeks ago that I responded to in more detail.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project