Skip to content
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

v3: Various fixes for Next.js projects and projects that use v2 and v3 together #1051

Merged
merged 12 commits into from
Apr 24, 2024

Conversation

ericallam
Copy link
Member

@ericallam ericallam commented Apr 22, 2024

  • Fixes an issue that was finding trigger dirs inside of .next and also was treating a v2 trigger Next.js App Router route as a v3 trigger dir.
  • Fixed the issue that was causing the dynamic import of msw to throw a ModuleNotFound error in Next.js
  • Extracted out all the non-SDK related exports from @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.
  • Export the Task and TaskOptions type, which fixes the Exported 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

Copy link

changeset-bot bot commented Apr 22, 2024

🦋 Changeset detected

Latest commit: 7dae81f

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@ericallam ericallam merged commit b68012f into main Apr 24, 2024
2 of 3 checks passed
@ericallam ericallam deleted the v3/fix-trigger-dirs branch April 24, 2024 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant