-
Notifications
You must be signed in to change notification settings - Fork 326
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
win32 arm64 Support #2735
Comments
That would be nice. I had to do the same workaround as OP to get my dev env. running. |
Hi, I've opened the PR #2997 in order to contribute. Feel free to help me with the configuration of bazel since it's the first time I touch this kind of stuff. |
Probably nothing, I think the binary exe run under emulation of x86_64 on the ARM64. |
I was not able to connect to a pg db with workerd for windows x64, under windows arm64. I'm using prisma + hono + wrangler@3 and the request was running indefinitely without error message or timeout. Only solution found was to rollback on wrangler@2. Just for your information if somebody has the same behavior. |
any updates on this ? |
Latest Surface Pro / Laptop line uses Snapdragon X ARM64 processors, continuing the Windows ARM trend. As an owner of one, this would be really convenient. I was intending to evaluate using Durable Objects for a new project, but even the small friction of setting up a WSL environment just to run the tutorial has me putting it off. |
What would you like?
Run a web application with Workerd on a computer with Win32-Arm64 OS.
Why is this needed?
With Asus recently releasing laptops with Qualcomm CPUs, this will be more and more requested.
See The Asus Vivobook S 15.
Other
I managed to start my Web app with workerd regardless.
By adding in "win32 arm64 LE": "@cloudflare/workerd-windows-64" in Install.js as a knownPackage. I dont know what side-effects this brings.
The text was updated successfully, but these errors were encountered: