Modules not resolved with adapter-cloudflare (buffer, stream, util, crypto) #3564
Comments
|
I am unable to replicate. Tested in a brand new Svelte demo project. System info: I also tried with node 16.3.0 in WSL without any errors. What are the contents of the project? Anything unusual in the config? Dependencies? |
|
Here is my svelte config, nothing fancy : Maybe the problem is linked to one of my dependencies ? Honestly no idea how to reproduce the bug other than that. The logs are not helping me to pinpoint the bug on any library with my current knowledge. The only things that I can think of is maybe the fact that the cloudflare adapter doesn't handle hooks.js or API routes (I have one POST request handler). But the package says that it supports all sveltekit features and those seems too basic to not be included in that phrasing. |
|
From the error message, it would certainly sound like the issue is that https://www.npmjs.com/package/jws uses Node APIs which are not available on Cloudflare. I imagine you would need to find another library that doesn't use these APIs. |
|
Do you have a recommendation on how can I find out which one(s) of my dependencies depends on jws ? (CTRL + F on my vscode doesn't find anything) |
|
That'd be EDIT: there are JWT libraries that use |
I just tested this library, it breaks as well with my cloudflare pages builds (and my local builds) : I am going to find another way to solve my needs without using JWT. |
|
I think you could solve that by disabling prerendering? Looks like it tried to use the WebCrypto API while prerendering, which wouldn't work (and presumably you wouldn't want to do that anyway).
Hah, you very well might be happier for it. |
|
Disabling prerendering in svelte.config.js solves the issue. But it's probably smarter to let it activated because some pages might need it, and deal with the error in the I guess problem solved, Should I close the issue ? |
Yeah, sounds reasonable. Though if you're using the package in a hook then that will effectively disable prerendering. If you're using it in an endpoint or something then you should be able to work around it.
That's usually what happens when an issue is resolved, yes 🙂 |
|
@simcolin You can use the following libraries to create your own JWS functions. They are tested in SvelteKit projects that are deployed on Cloudflare Workers. The following code example generates parts of JWT using the Custom functions can be written using the Web Crypto API and the TextEncoder. |
|
stripe uses these libraries, so can't use stripe on cloudfare? getting the same issues. |
I was able to get it to compile, using |
Describe the bug
The sveltekit build crash with current latest next versions of cloudflare adapter and sveltekit
Reproduction
use versions provided in system info
try to build
Logs
System Info
System: OS: Windows 10 10.0.19041 CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Memory: 8.79 GB / 15.92 GB Binaries: Node: 16.3.0 - F:\Program Files\nodejs\node.EXE npm: 7.16.0 - F:\Program Files\nodejs\npm.CMD Browsers: Chrome: 97.0.4692.71 Edge: Spartan (44.19041.423.0), Chromium (97.0.1072.69) Internet Explorer: 11.0.19041.1 npmPackages: @sveltejs/adapter-cloudflare: 1.0.0-next.9 => 1.0.0-next.9 @sveltejs/adapter-node: ^1.0.0-next.67 => 1.0.0-next.67 @sveltejs/adapter-static: ^1.0.0-next.26 => 1.0.0-next.26 @sveltejs/kit: next => 1.0.0-next.245 svelte: ^3.46.3 => 3.46.3Severity
blocking an upgrade
Additional Information
standard node adapter compiles without any problem
using
{ platform: 'node' }as build parameters for the cloudflare adapter fixes the build crash but break the cloudflare deploymentThe text was updated successfully, but these errors were encountered: