-
Notifications
You must be signed in to change notification settings - Fork 828
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: wrangler pages deploy throws misleading error when experimental:nodejs_compat_v2 is enabled #6288
Comments
I literally ran into this myself last night, so can confirm this is indeed happening. Will take a look! To clarify...this works as intended for Workers, just not for Pages |
@CarmenPopoviciu — is this still something you're digging into? |
@irvinebroque yes, planning to this week! |
@CarmenPopoviciu did you get a chance to look into this last week? |
Pete has a PR for it at #6511 |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which Cloudflare product(s) does this pertain to?
Wrangler
What version(s) of the tool(s) are you using?
3.57.1
What version of Node are you using?
v22.3.0
What operating system and version are you using?
Mac Sonoma 14.5
Describe the Bug
How to reproduce
Repro
With
experimental:nodejs_compat_v2
, runwrangler pages deploy
...This error isn't right — I already have
experimental:nodejs_compat_v2
enabled, but it's telling me I need to enable thenodejs_compat
flag.If I add the
node:
specifier tofs
, I get a different errorBut to the customer — that's what you told me in your docs I was supposed to enable :)
Effectively — we're just returning the same error we'd return if you enabled
nodejs_compat
(link to repro)What should we do about it?
When I run
wrangler pages deploy
withexperimental:nodejs_compat_v2
...nodejs_compat_v2
compat flag should be enabled (and theexperimental:
prefix properly removed, as is already current behavior for Workers)Please provide a link to a minimal reproduction
irvinebroque/remix-d1#8
Please provide any relevant error logs
No response
The text was updated successfully, but these errors were encountered: