3 ms·
I get why people would want to push this forward in general, but except in a case down the road, many years from now, is there a real case right now for running
by awongh 2y ago
I get why people would want to push this forward in general, but except in a case down the road, many years from now, is there a real case right now for running your typescript code without compiling it?
Maybe library compatibility?
My first reaction is that this just further fractures the ecosystem, where some codebases/libraries will have TS that is required to be compiled and some will not, adding a third kind of TS/JS code that's out there.
- JimDabell 2y ago> except in a case down the road, many years from now We’re not talking about the distant future. Node shipped its first version supporting type stripping six months ago.
- awongh 2y agoI'm not up to date on what people are working on, but I just mean that type stripping is probably not the final solution to a roadmap of node-typescript compatibility? That I would imagine there are other features being proposed that will continue to develop this compatibility?
- JimDabell 2y agoThe difference between type stripping and implementing other behaviour is precisely what is being flagged as a problem with enums in this thread. If you only have type stripping – which is the present day situation for Node users – then using enums will break TypeScript that you would otherwise be able to execute.
- mistercow 2y agoBeing able to set up a node project like a web server without configuring or maintaining any build steps is pretty nice.