LLRT Roadmap & Priorities
Below is a high level list of LLRTs priorities and roadmap items. Note that these are not final and are subject to change.
2024
- ~~Increased WinterCG compliance~~ ✅
- ~~SubtleCrypto~~ https://github.com/awslabs/llrt/issues/184 ✅
- ~~Switch to more activity maintained~~ QuickJS - Next Generation fork ✅
- Better documentation (website, examples, do's and dont's etc)
- ~~Partially native web streams~~✅
- ~~Increased release cadence~~✅
2025
- HTTP & HTTPs module
- PGO + PLO + Bolt/Propeller optimized binaries
- 1.0 release
- TLS sockets/connections
- WebSockets
- Native Streams
- Better unhandled promise rejection tracking
- Better local development experience
- Debugger
If reasonable, please consider to add a note on the expected AWS-managed LLRT runtime for Lambda service. It should slightly improve cold starts due to the runtime caching, making LLRT even more appealing to use
Have you considered adding stdin for reading user input?
https://github.com/quickjs-ng/quickjs/issues/374
The ideal situation is that the upstream qjs-ng and qjs will be merged, but it seems that this is not going well.
The ideal situation is that the upstream qjs-ng and qjs will be merged, but it seems that this is not going well.
We'll soon move to qjs-ng. We're waiting for https://github.com/DelSkayn/rquickjs/pull/369 and https://github.com/DelSkayn/rquickjs/pull/373 to be finalized. This is not to far away.
Very exciting 🎉
Would Partially native web streams look to cover this: https://github.com/awslabs/llrt/issues/318
or would that be more inline with 2025 Native Streams
Very exciting 🎉
Would
Partially native web streamslook to cover this: #318or would that be more inline with 2025
Native Streams
Likely the latter. We’d rather ship a more complete steams API than cut corners. But depending on how fast we can progress with the more feature complete stream API we can also do a lighter version similar to the spawn streams.
The roadmap sounds promising! I'm just wondering, if v1 is released, would LLTR become one of the default runtimes on AWS Lambda?
Will there be a way to read user input?
https://github.com/awslabs/llrt/issues/175
Are you planning on adding Intl support? I was unable to find a reference to the Intl api in the roadmap. TIA
I'd like to suggest adding node:async_hooks and especially AsyncLocalStorage and AsyncResource to the roadmap.
They'd be very helpful when it comes to observability-related use cases since they help library authors maintain state without risks of leaking data across Lambda invocations.
As a dependency to async_hooks, it's probably worth adding xray sdk support too (#628). A majority of our lambdas use xray tracing, and as such we can't migrate them to LLRT without losing that observability.
Any chance you could add #787 to the roadmap? Would be great to see this as part of a 1.0 release if not much sooner. LLRT is a perfect fit for lightweight CLIs & I could see usage growing significantly if it were easy to create a single executable.
Is there an ETA on the 1.0 release?