4 ms·
Coming to Next.js from Laravel, being able to hand things off to a long running worker is one of the things I missed the most. We're currently handling this wit
by adamkaz 3y ago
Coming to Next.js from Laravel, being able to hand things off to a long running worker is one of the things I missed the most. We're currently handling this with a non-ideal solution and will definitely check Trigger.dev out when you launch that feature.
- matt-aitken 3y agoGreat, you can subscribe to updates on our discussion here: https://github.com/triggerdotdev/trigger.dev/discussions/400 https://github.com/triggerdotdev/trigger.dev/discussions/400 We'll be updating it as we make progress and open it up for early testers.
- plastic_bag 3y agoMay I ask what made you to switch from Laravel to Next.js?
- phatskat 3y agoWould like to know this as well. I switched from my last company’s WordPress app over to our Laravel side of things (with Vue/Inertia on the front end) and I really liked it. I’ve heard of Next.js here and there but seeing in the context of “switched from Laravel” I’m very curious.