Jacob Hummer

📬 @sheremet-va since i notice you're not 👁 watching this repo https://github.com/tinylibs/tinyrainbow/watchers

> Changing the API will render this library useless. Especially because it doesn't work in Node. > it would be nice to treat Node.js as the "special case" What I...

> Nice suggestion! 👍 Where could we see the closest need in such feature? May be somewhere in typst? It's not really a thing I _need_ or something I even...

I think you could solve this by using export/import conditions which are an out-of-band way to detect what platform you're running on/bundled for. https://nodejs.org/api/packages.html#conditional-exports https://nodejs.org/api/packages.html#imports

Yes, I have been thinking along those lines. There are a few ideas for how this `typst` package could be used: 1. To auto-install the typst binary when a user...

> I'm curious to if you thought about merging step 1 and step 2 with the use of (napi-rs/deno-ops) to bind to the typst crates for cli/lib usage. To allow...

note to self: i was pointed to https://github.com/napi-rs/napi-rs/issues/796 wasm support seems to be on the horizon but not here until napi-rs v3? https://github.com/napi-rs/napi-rs/issues/1493

youre right a direct nodejs rust binding would be more powerful. in the future, that might be what happens! and the idea to avoid binding a typst.node and a typst.exe...

The reason PyInstaller doesn't like relative imports in its input files is a bit murky to me too, but I think it has to do with it just extracting it...

An update on the use case: I have solved my problem which was getting a PyInstaller build of Bikeshed for use in places without pip & Python: I fork &...