-
-
Notifications
You must be signed in to change notification settings - Fork 725
Feat: do we fancy a native Astro integration? #345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Of course, that would be amazing! Here's everything I can think of at the moment that would be nice to do to get astro support in (this isn't to say you should do these, just that they should be done at some point): |
Sounds like a good list. I might just tackle them as one-by-one PRs to make it scoped and easier to review and iterate while working to land these in officially. |
@ericallam I think you can remove the bullet-list you created as I copied it over to my opening comment body as a tasklist so it is easier to track. On that note, see first PR introduced for the astro package. |
Looks like this is now already shipped thanks to:
So I'd imagine we can close? |
@lirantal yep this is done, thanks a lot 🤩 |
Uh oh!
There was an error while loading. Please reload this page.
Hey folks!
Similar to the Express and Next.js packages, do we want to have a native Astro integration package as part of the officially provided packages from Trigger.dev?
See the following resources for more context:
Of course, that would be amazing! Here's everything I can think of at the moment that would be nice to do to get astro support in (this isn't to say you should do these, just that they should be done at some point):
The text was updated successfully, but these errors were encountered: