-
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 cannot be used in Cloudflare Pages #6346
Comments
Thanks for reporting this. The We plan to investigate conditional importing for these dependencies within the next 2 weeks. |
Hey, just wondering if there's any update? CF Pages is becoming an increasingly popular deployment platform :) |
We are actively working on a fix for this, aiming to ship it by next week. |
@fell-lucas, can you please try this version |
Hey, unfortunately when building with the version you mentioned, I get this new Vite error:
This error is probably related to this: #7071 |
@fell-lucas apologies for the delay but the past couple of weeks have been hectic with the release of our new Dashboard. Can you please try with |
📜 Description
We get build errors when deploying to CF pages because the package imports unsupported node dependencies.
Even though we are not using the JSON Schema features of @novu/framework, we still get these import errors. Is it possible to ask for conditional importing of the problematic dependencies?
👟 Reproduction steps
workflow
import from @novu/framework.api/novu/+server.ts
and import theserve
function from @novu/framework/sveltekit👍 Expected behavior
Not throw build errors because we're not relying on JSON Schema to create our workflows.
👎 Actual Behavior with Screenshots
Novu version
Novu SaaS
npm version
NA
node version
NA
📃 Provide any additional context for the Bug.
@novu/framework version: 2.0.0-canary.5
👀 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?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: