I have a page with a simple function using `export async function onRequestPost(context) {` I am tr

NNoOneInParticulate I have a page with a simple function using `export async function onRequestPost(...

K

kian•1/9/24, 8:31 PM

context.request

context.request

is the Request Web API, where the

body

body

body

body property is a ReadableStream

K

kian•1/9/24, 8:32 PM

If you want to access the body, there are helper methods on

Request

Request

like

text()

text()

text()

text() &

json()

json()

json()

json(). So, if your request body is JSON, then you'd do...

const json = await context.request.json()
console.log(json.property);

const json = await context.request.json()
console.log(json.property);

const json = await context.request.json()
console.log(json.property);

const json = await context.request.json()
console.log(json.property);

N

NoOneInParticulateOP•1/9/24, 8:32 PM

Thank you!

K

kian•1/9/24, 8:32 PM

json()

json()

json()

json() is basically

JSON.parse(await request.text())

JSON.parse(await request.text())

JSON.parse(await request.text())

JSON.parse(await request.text()), you'll get an object back

T

TigersWay•1/10/24, 9:22 AM

Trying to rewrite some old workers to pages functions I have a "strange" error message:

Your worker created multiple branches of a single stream...

Your worker created multiple branches of a single stream...

Your worker created multiple branches of a single stream...

Your worker created multiple branches of a single stream...
The

GET

GET

are working fine, but nothing else even with "empty" APIs.

export const onRequest: PagesFunction = async (context) => {
  console.log('TRACKING');
  return new Response();
};

export const onRequest: PagesFunction = async (context) => {
  console.log('TRACKING');
  return new Response();
};

export const onRequest: PagesFunction = async (context) => {
  console.log('TRACKING');
  return new Response();
};

export const onRequest: PagesFunction = async (context) => {
  console.log('TRACKING');
  return new Response();
};

G

gabrielstuff•1/10/24, 9:15 PM

Hello, I'm trying to use page functions to run

ytdl-code

ytdl-code

ytdl-code

ytdl-code but got errors everywhere :

✘ [ERROR] 14 error(s) and 0 warning(s) when compiling Worker.
✘ [ERROR] Could not resolve "buffer"

✘ [ERROR] 14 error(s) and 0 warning(s) when compiling Worker.
✘ [ERROR] Could not resolve "buffer"

✘ [ERROR] 14 error(s) and 0 warning(s) when compiling Worker.
✘ [ERROR] Could not resolve "buffer"

✘ [ERROR] 14 error(s) and 0 warning(s) when compiling Worker.
✘ [ERROR] Could not resolve "buffer"

I' trying to understand if page function support external packages at all

K

kian•1/10/24, 9:17 PM

Yes, but Workers and Functions aren't Node so they don't have Node built-ins.

G

gabrielstuff•1/10/24, 9:21 PM

ok thanks, so are we able to use npm package in them ?

G

gabrielstuff•1/10/24, 9:21 PM

or maybe esm.sh import ?

G

gabrielstuff•1/10/24, 9:22 PM

Reading the doc, I thought i could simply adjust the netlify functions path, rewrite and run. But it looks like it is not the case exactly.

Ggabrielstuff ok thanks, so are we able to use npm package in them ?

I

Isaac McFadyen•1/10/24, 9:22 PM

You can use NPM packages, but you cannot use a Node built-in module, which ytdl-code does (

buffer

buffer

buffer

buffer)

I

Isaac McFadyen•1/10/24, 9:22 PM

If there's an alternative package that doesn't use

buffer

buffer

buffer

buffer then you might be able to use that

I

Isaac McFadyen•1/10/24, 9:23 PM

You could also patch

ytdl-code

ytdl-code

ytdl-code

ytdl-code to import from

node:buffer

node:buffer

node:buffer

node:buffer instead and then use Workers NodeJS compat: https://developers.cloudflare.com/workers/runtime-apis/nodejs/

G

gabrielstuff•1/10/24, 9:24 PM

ok, I see. No I do not think so. What is the alternative when people rely on package with node built-in module ? Any cloudflare product

G

gabrielstuff•1/10/24, 9:24 PM

(going to read the code of ytdl-core

but the patch path seems a bit long to me)

Ggabrielstuff ok, I see. No I do not think so. What is the alternative when people rely on pac...

I

Isaac McFadyen•1/10/24, 9:25 PM

There is no Cloudflare product that allows build-in modules unfortunately - it's either patching it to use

node:buffer

node:buffer

node:buffer

node:buffer or finding an alternative package.

I

Isaac McFadyen•1/10/24, 9:25 PM

Actually, you might be able to.

I

Isaac McFadyen•1/10/24, 9:25 PM

Try adding
node_compat = true
node_compat = true
to your
wrangler.toml
wrangler.toml
: https://developers.cloudflare.com/workers/wrangler/configuration/#node-compatibility

I

Isaac McFadyen•1/10/24, 9:25 PM

It's the older form of Node compat so it won't work as well for some things but it might work.

I

Isaac McFadyen•1/10/24, 9:27 PM

Oh this is Pages. Hmmm.

I

Isaac McFadyen•1/10/24, 9:27 PM

Not sure if you can use node_compat in Pages

G

gabrielstuff•1/10/24, 9:27 PM

Reading the code, as https://github.com/fent/node-ytdl-core/blob/master/package.json#L39 depends on m3u8stream,miniget and sax I guess I should also patch this packages ?

I

Isaac McFadyen•1/10/24, 9:28 PM

Yeah, probably. Assuming they use node built-ins

IIsaac McFadyen Not sure if you can use node_compat in Pages

G

gabrielstuff•1/10/24, 9:28 PM

https://developers.cloudflare.com/workers/runtime-apis/nodejs/#enable-nodejs-with-pages-functions apparently yes it's possible

G

gabrielstuff•1/10/24, 9:28 PM

I did that but no effect

I

Isaac McFadyen•1/10/24, 9:28 PM

That would be the newer nodejs_compat (similar names, it's a bit confusing) which requires you to change your imports to

node:buffer

node:buffer

node:buffer

node:buffer unfortunately.

G

gabrielstuff•1/10/24, 9:28 PM

I locally tested with

npx wrangler pages dev --compatibility-flags="nodejs_compat" -- npm run dev

npx wrangler pages dev --compatibility-flags="nodejs_compat" -- npm run dev

npx wrangler pages dev --compatibility-flags="nodejs_compat" -- npm run dev

npx wrangler pages dev --compatibility-flags="nodejs_compat" -- npm run dev

I

Isaac McFadyen•1/10/24, 9:28 PM

I don't think the

node_compat

node_compat

node_compat

node_compat (the original one) works with Pages.

G

gabrielstuff•1/10/24, 9:29 PM

oh ! I see

node_compat

node_compat

node_compat

node_compat vs

nodejs_compat

nodejs_compat

not the little

js

js

js

js hehe

G

gabrielstuff•1/10/24, 9:30 PM

ok lets dive a bit into built-in stuff

G

gabrielstuff•1/10/24, 9:30 PM

and see what's possible

G

gabrielstuff•1/10/24, 9:31 PM

any recommandation to check if a package rely on node built-in module ?

I

Isaac McFadyen•1/10/24, 9:34 PM

Other than deploying the package to test, not really. I suppose you could

npm install

npm install

npm install

npm install it and then search for

buffer

buffer

buffer

buffer,

fs

fs

fs

fs, etc in node_modules but that might not catch everything.

G

gabrielstuff•1/10/24, 9:50 PM

Thanks !

Ggabrielstuff any recommandation to check if a package rely on **node built-in module** ?

R

Robin•1/11/24, 7:04 AM

@auth/sveltekit! I have the same issue on cf pages functions.

> Using @sveltejs/adapter-cloudflare
21:38:26.511    ✘ [ERROR] Could not resolve "crypto"
21:38:26.512    
21:38:26.512        .svelte-kit/output/server/chunks/hooks.server.js:4:26:
21:38:26.513          4 │ import * as crypto$1 from "crypto";
21:38:26.513            ╵                           ~~~~~~~~
21:38:26.513    
21:38:26.513      The package "crypto" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
21:38:26.514    
21:38:26.516    ✘ [ERROR] Could not resolve "node:buffer"
21:38:26.517    
21:38:26.517        .svelte-kit/output/server/chunks/hooks.server.js:6:23:
21:38:26.517          6 │ import { Buffer } from "node:buffer";
21:38:26.517            ╵                        ~~~~~~~~~~~~~
21:38:26.517    
21:38:26.517      The package "node:buffer" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
21:38:26.517    

...

21:38:26.532    error during build:
21:38:26.532    Error: Build failed with 4 errors:
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:4:26: ERROR: Could not resolve "crypto"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:6:23: ERROR: Could not resolve "node:buffer"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:7:26: ERROR: Could not resolve "node:crypto"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:9:22: ERROR: Could not resolve "node:util"

> Using @sveltejs/adapter-cloudflare
21:38:26.511    ✘ [ERROR] Could not resolve "crypto"
21:38:26.512    
21:38:26.512        .svelte-kit/output/server/chunks/hooks.server.js:4:26:
21:38:26.513          4 │ import * as crypto$1 from "crypto";
21:38:26.513            ╵                           ~~~~~~~~
21:38:26.513    
21:38:26.513      The package "crypto" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
21:38:26.514    
21:38:26.516    ✘ [ERROR] Could not resolve "node:buffer"
21:38:26.517    
21:38:26.517        .svelte-kit/output/server/chunks/hooks.server.js:6:23:
21:38:26.517          6 │ import { Buffer } from "node:buffer";
21:38:26.517            ╵                        ~~~~~~~~~~~~~
21:38:26.517    
21:38:26.517      The package "node:buffer" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
21:38:26.517    

...

21:38:26.532    error during build:
21:38:26.532    Error: Build failed with 4 errors:
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:4:26: ERROR: Could not resolve "crypto"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:6:23: ERROR: Could not resolve "node:buffer"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:7:26: ERROR: Could not resolve "node:crypto"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:9:22: ERROR: Could not resolve "node:util"

> Using @sveltejs/adapter-cloudflare
21:38:26.511    ✘ [ERROR] Could not resolve "crypto"
21:38:26.512    
21:38:26.512        .svelte-kit/output/server/chunks/hooks.server.js:4:26:
21:38:26.513          4 │ import * as crypto$1 from "crypto";
21:38:26.513            ╵                           ~~~~~~~~
21:38:26.513    
21:38:26.513      The package "crypto" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
21:38:26.514    
21:38:26.516    ✘ [ERROR] Could not resolve "node:buffer"
21:38:26.517    
21:38:26.517        .svelte-kit/output/server/chunks/hooks.server.js:6:23:
21:38:26.517          6 │ import { Buffer } from "node:buffer";
21:38:26.517            ╵                        ~~~~~~~~~~~~~
21:38:26.517    
21:38:26.517      The package "node:buffer" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
21:38:26.517    

...

21:38:26.532    error during build:
21:38:26.532    Error: Build failed with 4 errors:
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:4:26: ERROR: Could not resolve "crypto"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:6:23: ERROR: Could not resolve "node:buffer"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:7:26: ERROR: Could not resolve "node:crypto"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:9:22: ERROR: Could not resolve "node:util"

> Using @sveltejs/adapter-cloudflare
21:38:26.511    ✘ [ERROR] Could not resolve "crypto"
21:38:26.512    
21:38:26.512        .svelte-kit/output/server/chunks/hooks.server.js:4:26:
21:38:26.513          4 │ import * as crypto$1 from "crypto";
21:38:26.513            ╵                           ~~~~~~~~
21:38:26.513    
21:38:26.513      The package "crypto" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
21:38:26.514    
21:38:26.516    ✘ [ERROR] Could not resolve "node:buffer"
21:38:26.517    
21:38:26.517        .svelte-kit/output/server/chunks/hooks.server.js:6:23:
21:38:26.517          6 │ import { Buffer } from "node:buffer";
21:38:26.517            ╵                        ~~~~~~~~~~~~~
21:38:26.517    
21:38:26.517      The package "node:buffer" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
21:38:26.517    

...

21:38:26.532    error during build:
21:38:26.532    Error: Build failed with 4 errors:
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:4:26: ERROR: Could not resolve "crypto"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:6:23: ERROR: Could not resolve "node:buffer"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:7:26: ERROR: Could not resolve "node:crypto"
21:38:26.532    .svelte-kit/output/server/chunks/hooks.server.js:9:22: ERROR: Could not resolve "node:util"

R

Robin•1/11/24, 7:09 AM

https://developers.cloudflare.com/workers/runtime-apis/nodejs/#enable-nodejs-from-the-cloudflare-dashboard suggests that those nodejs packages should work, yet they aren't. any help?

Node.js compatibility · Cloudflare Workers docs

Implemented Node.js runtime APIs and enablement instructions for your Worker project.

RRobin https://developers.cloudflare.com/workers/runtime-apis/nodejs/#enable-nodejs-fro...

H

Hello, I’m Allie!•1/11/24, 7:12 AM

This is a build-time error, not a runtime error. SvelteKit doesn’t know that you are enabling node compatibility, so it throws an error

H

Hello, I’m Allie!•1/11/24, 7:13 AM

You need to mark those node dependencies as external

HHello, I’m Allie!You need to mark those node dependencies as external

R

Robin•1/11/24, 7:18 AM

Oh thanks, do you have a resource how to configure that?

RRobin Oh thanks, do you have a resource how to configure that?

H

Hello, I’m Allie!•1/11/24, 7:32 AM

Not sure. I think I remember you have to do it via the Vite Options in SvelteKit. Might be able to dig it up later if you can't find it.

HHello, I’m Allie!Not sure. I think I remember you have to do it via the Vite Options in SvelteKit...

R

Robin•1/11/24, 7:45 AM

would be great, can't find any resource

G

gabrielstuff•1/11/24, 2:52 PM

Oh !

HHello, I’m Allie!Not sure. I think I remember you have to do it via the Vite Options in SvelteKit...

G

gabrielstuff•1/11/24, 2:53 PM

So, it would work for my package also ?

G

gabrielstuff•1/11/24, 2:53 PM

It's a bit hard to understand your choice on the

node_compat

node_compat

node_compat

node_compat vs

nodejs_compat

nodejs_compat

G

gabrielstuff•1/11/24, 2:53 PM

On netlify, we

just

just

npm i -S and import, on Google we edit the package.json and it

just

just

work.

G

gabrielstuff•1/11/24, 2:54 PM

On cloudflare, everything is super smooth and better except this part.

G

gabrielstuff•1/11/24, 2:54 PM

Disclamer, I ended up using Google Cloud Functions but I've preferred not to

K

kian•1/11/24, 2:57 PM

Workers and Functions aren’t Node, Netlify and GCF are.

K

kian•1/11/24, 2:57 PM

node_compat are build time polyfills and nodejs_compat is a subset of modules built into the runtime

T

Tuấn Anh•1/12/24, 7:08 AM

Hello, I am using React JS and page function, how can I binding KV and use it in my react application locally, this is the code to access my local KV but it is not working, when I deploy then it works normally. Thanks a lot for your answers!

I have a page with a simple function using `export async function onRequestPost(context) {` I am tr

Similar Threads

Similar Threads

Similar Threads