Open samejr opened 1 year ago
/bounty $200
## 💎 $200 bounty • Trigger.dev (YC W23)
/attempt #448
with your implementation plan/claim #448
in the PR body to claim the bounty/livestream
once liveThank you for contributing to triggerdotdev/trigger.dev!
Can you assign this to me?
This one is yours 👍
Thanks, looks like Redwood is tough for people :) (just kidding @ajcwebdev)
@rishi-raj-jain: Reminder that in 7 days the bounty will become up for grabs, so please submit a pull request before then 🙏
I'm working on it.
The bounty is up for grabs! Everyone is welcome to /attempt #448
🙌
/tip @rishi-raj-jain $200
/tip $200 @rishi-raj-jain
🎉🎈 @rishi-raj-jain has been awarded $200! 🎈🎊
This issue is currently on pause because RedwoodJS currently only supports the Yarn package manager: https://github.com/redwoodjs/redwood/issues/2907.
This means that it doesn't play nicely inside our repo. If we could get it work nicely we'd also have to make it so all the instructions in the app and docs only used yarn.
Additionally here's a comment with a video showing the problem: https://github.com/triggerdotdev/trigger.dev/pull/598#issuecomment-1754963307
Is this issue still on pause? @matt-aitken
Hey, we won’t be providing an official Redwood package for v2. Instead, v3 will be shipping in a few weeks and will not require any framework specific code: https://trigger.dev/blog/v3-announcement
/attempt #448
@HyperDanisH: Another person is already attempting this issue. Please don't start working on this issue unless you were explicitly asked to do so.
Hey @HyperDanisH this bounty has already been claimed
@samejr It's fine, I can further look for other bounties.
Build support for Redwood into Trigger.dev
Please make sure to use Typescript for all code
Task 1 - Redwood Adaptor
packages
calledredwood
examples/redwood
folder. Include a basic Job in Trigger.dev, e.g. a simple Job that just does a delay inside it. Screen grab the full Run dashboard page showing it successfully worked. Here are examples of how to do cross-project references in package.json and tsconfig.json.Task 2 – Add a README.md file
packages/redwood
folder and copy in the contents frompackages/nextjs/README.md
. Adjust the wording to reference Redwood where needed, including updating the the URLs.Task 3 – Write the documentation
manual-setup-redwood.mdx
folder in/docs/_snippets/
. Use this file to write your documentation, overwriting any contents of that file. Follow the structure of this Next.js example for reference when writing yours.client-adaptors.mdx
page with the framework you’ve worked on.Task 4 – Update the webapp onboarding
route.tsx
page located in_app.orgs.$organizationSlug.projects.$projectParam.setup.redwood
replace the<FrameworkComingSoon/>
component with your new onboarding steps. Follow the same structure as the Next.js example when creating your own. Ignore the very top step for adding this framework to a new project, just focus on the steps to add it to an existing project (so don’t include the<RadioGroup/>
toggle selector at the top). Make sure you also include theuseProjectSetupComplete();
hook at the top of the page – this triggers a particle effect when the new job is successfully created and redirects to the Jobs list 🥳 .FrameworkSelector.tsx
file, add “supported” to the framework you’ve worked on.TRI-1251