-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
🐛 Bug Report: @novu/framework: 2.4.0 Breaking imports #6954
Comments
Firstly, apologies for this disruption! Version We have an open PR (#6812) that will ship soon, providing Could you please share your use-case for accessing the In the interim, please import change your import { Workflow } from `@novu/framework/internal`; It's important to note that the |
Thank you for the response @rifont. We have a plugin system and this error happens in the plugin we wrote for novu. The Workflow type is used in the interface declaration for that Plugin. We were able to work around that by using ReturnType, which solved the build failure.
Reverting @novu/framework: 2.3.0 fixes this, and everything works as before |
Thank you for sharing more information about your setup. In It appears that your runtime environment doesn't make that global
|
Never mind the above, I see you are using Node 18 from the original description. Please raise a separate issue for the |
I raised a new issue (#6982) for the |
Thank you @rifont , got side tracked with other priorities. Will add more details in the new issue soon. |
The import { Workflow } from '@novu/framework'; |
📜 Description
version 2.4.0 no longer exports the type Workflow, causing imports to break in typescript
👟 Reproduction steps
install latest @novu/framework
Try importinng the Workflow type
👍 Expected behavior
Type should be exported and should be accessible in client code, where type inference may not be straight forward, for example in a custom monorepo
👎 Actual Behavior with Screenshots
Novu version
Novu SaaS
npm version
9.5.1
node version
18.16.0
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: