v3: Various fixes for Next.js projects and projects that use v2 and v3 together #1051
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.
.next
and also was treating a v2 trigger Next.js App Router route as a v3 trigger dir.msw
to throw a ModuleNotFound error in Next.js@trigger.dev/core/v3
and moved them into separate exports (e.g.@trigger.dev/core/v3/zodNamespace
. From now on only stuff needed in the SDK should be exported from@trigger.dev/core/v3
.Task
andTaskOptions
type, which fixes theExported variable 'helloWorldTask' has or is using name 'Task' from external module "<project>/node_modules/@trigger.dev/sdk/dist/v3/index" but cannot be named
error