Uh oh!
There was an error while loading. Please reload this page.
[docs] Document NestJS setup + Vercel e2e tests - #850
Merged
Conversation
Loading
Uh oh!
There was an error while loading. Please reload this page.
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds some fixes for the NestJS workbench app to make it work for Vercel deployment, and adds the "Getting Started" guide for NestJS to the docs.
I wasn't able to find an easy way to plug our builder into the NestJS build system, so I ended up (after a lot of back and forth with claude) going with a SWC plugin, since NestJS can use SWC directly. The setup has an extra step (having to call
npx @workflow/nest init).Hence, I'm not too happy with this, but I think it's worth merging/launching, since it's better than having no implementation, and it works fine for a test project (I ran through the getting-started steps). Can ITG after, more important things in the pipeline