Q: Better TypeScript support? #399
-
|
Are there any plans to better support TypeScript? Why was the |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
|
It seems reasonable to extend |
Beta Was this translation helpful? Give feedback.
-
|
Zx dropped *.ts support as it requires CJS, and cjs was dropped as it was causing a lot of problems. |
Beta Was this translation helpful? Give feedback.
-
|
Since the .mjs extension is supported, it seems we can build/transpile TS to JS in a .mjs and just run that, right? Are there any details required to do such a build to make a TS project (like in VSCode) fully compatible with zx? The doc page on TypeScript is only vaguely helpful, as it doesn't actually mention TypeScript. 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
TS integration is possible. But requires some boilerplate. |
Beta Was this translation helpful? Give feedback.
-
|
OK, that's fair. It seems clear that "Better TypeScript Support" is a "wont fix" type resolution for this. Or, maybe the ticket should be modified into a request for new documentation with boilerplate for TS support? As a newcomer, I see TS as a convenience but not a requirement. It would be nice to see TS support but I have no problem continuing with my research into zx without it. |
Beta Was this translation helpful? Give feedback.
-
|
Well, there is some progress: |
Beta Was this translation helpful? Give feedback.
-
|
We have expanded the documentation section dedicated to TS configuration: https://google.github.io/zx/typescript Lines 84 to 88 in e1b66cb |
Beta Was this translation helpful? Give feedback.
We have expanded the documentation section dedicated to TS configuration: https://google.github.io/zx/typescript
Proven examples can also be found in the project tests.
zx/package.json
Lines 84 to 88 in e1b66cb