So many bugs, Is this package production ready?

[liho00]

reproduce repo: https://github.com/liho00/nestjs-temporal

[yamiyukiharu]

how is this repo, nestjs-temporal-core related to nestjs-temporal ?

[liho00]

@yamiyukiharu
ended up i used nestjs-temporal instead, this package nestjs-tempore-core author is not helping at all, and not functioning
dont waste your time using this package

use this instead bro https://github.com/KurtzL/nestjs-temporal
even tho the package have 2 years did not upgraded but still work like charm and easy to use!

[yamiyukiharu]

what a waste, i really like the interface and the decorators from this package though. Thanks for the info!

[liho00]

@yamiyukiharu seems like the author just published a new version, probably works now,
may be you can give it a try and let us know haha

[harsh-simform]

Hi @liho00, @yamiyukiharu — thanks for the honest feedback and taking the time to share your experiences.

First off, I completely understand the frustration. nestjs-temporal-core is still evolving, and I acknowledge that it hasn’t yet reached full production maturity for all use cases. That said, the goal has always been to provide a more ergonomic and NestJS-native abstraction for working with Temporal — including better decorators, DI, and structure.

The project is under active development, and I truly appreciate issue reports like these. If there are specific bugs or blockers you encountered, I'd love to get those resolved. PRs and collaboration are very welcome.

That said, for those needing immediate stability and simplicity, nestjs-temporal by @KurtzL is indeed a solid alternative — and I respect the choice to use what works best in your production stack.

Thanks again for checking out the project — and if you’re still open to contributing or sharing what didn’t work, I’m all ears. 🙌

[frct1]

@harsh-simform
There is no easy way to implement workflow decorator because of only reason that workflows are running inside V8 VM. So you need to do some sort of transpiling which is over engineering. The best way is to just allow users write "clean" workflows as it is designed initially by Temporal.

[yamiyukiharu]

thats kinda sad, I came here for the workflow decorators. Let me familiarise more with the setup and hopefully i can contribute

[frct1]

thats kinda sad, I came here for the workflow decorators. Let me familiarise more with the setup and hopefully i can contribute

Lib itself seems to be "vibe-coded", that's why it's not working as expected (and would not which is obv). Use @KurtzL's lib/

[harsh-simform]

@frct1 @yamiyukiharu
Totally fair to say parts of this are “vibe-coded” 😅 — there’s a lot to handle under the hood, and it’s definitely a time-consuming process. I’m an active full-time developer at an org, and this is a side project I’ve been building with the help of AI tools.

It’s not perfect (yet), but I’m still actively working on making nestjs-temporal-core easy to integrate for more use cases.

From my side — I’d just say instead of calling it not worth using, feel free to contribute if you're interested. Or of course, use any library that suits your needs better — no hard feelings at all! 😊

I’m always open to feedback or suggestions. Just bear with me if I’m a bit slow to respond — time is tight, but I’m committed to improving it.

[mjameswh]

That said, the goal has always been to provide a more ergonomic and NestJS-native abstraction for working with Temporal — including better decorators, DI, and structure.

@harsh-simform As the primary maintainer of the Temporal TypeScript SDK, I really appreciate your efforts on bridging NestJS and Temporal. I would definitely like to see more ecosystem integrations like this, but our team unfortunately can't prioritize that effort just now.

As I mentioned on a related ticket, actually exploiting Nest's DI from inside the Workflow sandbox is simply impossible, as @nestjs/common and @nestjs/core packages themselves depend on various non-deterministic-safe modules.

I have a few ideas however of customizations to the bundling process that could be used to exploit such decorators in a way that they could serve a dual purpose, both outside the sandbox (i.e. interacting with Nest's DI) and inside the sandbox. I think that would provide the kind of DX that you are looking for.

If you are interested in discussing and exploring some of those ideas, I would be happy to share some of my thoughts on the subject. I'd suggest however that we discuss that on the official TS SDK repo, so that it is more accessible to other interested parties. What do you think?

[harsh-simform]

Hi @mjameswh — thank you for the thoughtful input and for clarifying some of the technical limitations around DI and the Workflow sandbox.

I understand the concerns regarding the use of NestJS modules inside the sandbox, and it's helpful to hear confirmation that this isn’t currently feasible without non-trivial workarounds. That said, I’m definitely interested in learning more about the ideas you mentioned regarding bundling customizations or dual-purpose decorators.