I don't know if I'm the only one experiencing this: It's too hard to find the download link from their website.
Readit NewstheThree commented on I tried Gleam for Advent of Code blog.tymscar.com/posts/gl... · Posted by u/tymscar
theThree commented on Pipelining in psql (PostgreSQL 18) postgresql.verite.pro/blo... · Posted by u/tanelpoder
I developed a JS pg client that use pipeline mode by default: https://github.com/stanNthe5/pgline
I’m not a heavy JS/TS dev so here’s an honest question: why not use Bun and forget about node? Sure I understand that not every project is evergreen but isn’t Bun a much runtime in general? It supports TS execution from day 1, has much faster dependency resolution, better ergonomics… and I could keep going.
I know I’m just a single data point but I’ve had a lot of success migrating old node projects to bun (in fact I haven’t used node itself since Bun was made public)
Again, I might be saying something terribly stupid because JS/TS isn’t really my turf so please let me know if I’m missing something.
I'm using Bun, but I avoid using any Bun.* function, because I don't want to bind my typescript project to a runtime.
Don’t forget the native typescript transpiler which reduces the complexity a lot for those using TS
It's still not ready for use. I don't care Enum. But you can not import local files without extensions. You can not define class properties in constructor.
Deleted Comment
theThree commented on Run TypeScript code without worrying about configuration tsx.is/... · Posted by u/nailer
Newer versions of node can run typescript directly[1]. The one where types are simply stripped is considered stable[2] (but you can’t use syntax that node doesn’t understand, such as enums).
They’re working on making features work that require some transpilation as well
[1]: https://nodejs.org/en/learn/typescript/run-natively [2]: https://github.com/nodejs/node/pull/58643
It still have issues. Example: `import foo from "./Foo"` doesn't work. You have to `import foo from "./Foo.ts"`