Repository navigation
Release node.js 24 support for riverqueue npm package #1546
Description
I'm working on adding river to our typescript+go stack and can see that the node26 requirements were loosened 2 weeks ago to node24, but the latest 0.2.0 version doesn't have this change yet.
Could a new version be released so we don't have to patch the package locally?
Activity
Nick-Lucas commentedon Oct 26, 2026
As an aside, it might be better to externalise the polyfill but document it as a requirement, plus in runtime-support check that it exists and throw the same as an error.
Importing a package and globalThis being mutated with a future API as a side effect isn't ideal when there are 3 polyfills for this API and applications may be using an alternative one, as a codebase could end up with a different winner when code changes and subtly change behaviour/bundles
brandur commentedon Oct 26, 2026
@Nick-Lucas Good point on the polyfill. Let me take a quick look at that. I'll try to get a new release cut by EOD.
OOC: Are you guys planning on using the new polyglot features in the sense that you have two River engines in each language running simultaneously?
Nick-Lucas commentedon Oct 26, 2026
🙏 thank you!
Still a little early to say for certain, but one of our go services uses river already and we like the idea of having 1 tool that we understand well. My current work on the application side (typescript) needs to be bridged over into our go services for some sandbox orchestration, so the idea of typescript enqueuing/scheduling tasks and crossing the boundary to a go service picking up the work is very attractive. This all surrounds building a custom "World" for the Vercel Workflow SDK which is typescript only, and their postgres world uses graphile-worker which doesn't benefit from being cross-language so the polyglot option did draw us toward you guys
brandur commentedon Oct 27, 2026
@Nick-Lucas Alright, want to give https://github.com/riverqueue/river/releases/tag/js%2Fv0.3.0 a shot?
Great! Okay, thanks for the extra context. Let us run into any issues — we usually don't hear from our users and we're definitely interested in how polyglot integrations turn out when we're able to find them.
Nick-Lucas commentedon Oct 27, 2026
Upgraded and things are looking good so far, thanks for the fast turnaround!
Happy to connect down the line if you want to talk use cases and feedback a bit too :)
brandur commentedon Oct 27, 2026
SG and no problem! Love that things are working so far.
Sign me up!