You can kind of do that like this... ```js for (const property in req) { console.log(`${property}

You can kind of do that like this...

for (const property in req) {
  console.log(`${property}: ${req[property]}`);
}

for (const property in req) {
  console.log(`${property}: ${req[property]}`);
}

for (const property in req) {
  console.log(`${property}: ${req[property]}`);
}

for (const property in req) {
  console.log(`${property}: ${req[property]}`);
}

kianOP•8/22/23, 5:25 PM

Basically, properties on the Web API types are typically non-enumerable (so not picked up by

Object.keys()

Object.keys()

console.log()

console.log()

) and they're also on the prototype (so not picked up by

Object.getOwnPropertyNames()

Object.getOwnPropertyNames()

which looks at the instance) - but there are ways to print out what's on them.

Kkian You can kind of do that like this... ```js for (const property in req) { cons...

kianOP•8/22/23, 5:26 PM

kianOP•8/22/23, 5:27 PM

It's an issue mostly unique to Workers - you can

console.log

console.log

a Web API type in Node/Browsers/etc

Torzak•8/22/23, 5:28 PM

Very interesting information!

Original message was deleted

Johtozo•8/22/23, 6:33 PM

Found my problem. I wasn't running wrangler on the project directory itself and was running above it, since I have a collection of directories... silly me :- P works dandy now

smattmyers•8/24/23, 4:13 PM

Do I need to add routes to my project in order to get my functions to deploy? I used wrangler to generate an Angular Universal SSR Pages project and I added /functions directory to my root directory, but it does not seem like it's getting deployed, and the routes are definitely not working.

smattmyers•8/24/23, 5:51 PM

that makes sense...thanks!

xdeq•8/25/23, 11:02 PM

No changes were made to the project, but after a successful build at the very end the following error started to appear. What is it and where did it come from?
(nuxt3, nitro, cloudflare-pages preset)

James•8/25/23, 11:15 PM

I would guess one of your dependencies got updated

xdeq•8/25/23, 11:16 PM

@cherryjimbo No packages have been updated / removed / added

James•8/25/23, 11:17 PM

Are you pinning specific dependency versions and using a lockfile? If you're using versions like

^1.0.0

^1.0.0

(note the

), then any version compatible with

1.0.0

1.0.0

could be installed

James•8/25/23, 11:17 PM

As far as I know, nothing on the Pages end has changed, so something in your project must have, be in a dependency, or sub-dependency, etc.

James•8/25/23, 11:17 PM

My first recommenedation would be to try and reproduce locally, doing a completely fresh install of the project

Sam•8/26/23, 6:47 AM

I'm struggling to implement a Pages function on a local repository. I have a repository with the following structure:

|---- public
| index.html
|---- functions
| getFeed.js

My index.html looks like this:

<html>
<head>
    <script src="https://unpkg.com/htmx.org@1.9.4"></script>
    <script src="https://unpkg.com/hyperscript.org@0.9.11"></script>
</head>
<script>
function loadIndex() {
    console.log('test');
    htmx.ajax('GET', '/getFeed', {target: "#swap", headers: {
    }})
}
</script>
<body onload="loadIndex()">
...
</body>
</html>

<html>
<head>
    <script src="https://unpkg.com/htmx.org@1.9.4"></script>
    <script src="https://unpkg.com/hyperscript.org@0.9.11"></script>
</head>
<script>
function loadIndex() {
    console.log('test');
    htmx.ajax('GET', '/getFeed', {target: "#swap", headers: {
    }})
}
</script>
<body onload="loadIndex()">
...
</body>
</html>

When I load the site, I get a 404 error for the /getFeed request. I'm not sure if this is a problem with my directory setup, my routing, loading htmx, or anything else. Can someone help me address this?

Sam•8/26/23, 6:49 AM

The contents of my

functions/getFeed.js

functions/getFeed.js

file are currently

export const onRequestGet = () => {
  return new Response("Hello, world!")
}

export const onRequestGet = () => {
  return new Response("Hello, world!")
}

And it's still returning 404

slagathor•8/26/23, 7:45 PM

Do functions work with NextJS deployments? Wrangler doesn't seem to be picking up my functions.

Sslagathor Do functions work with NextJS deployments? Wrangler doesn't seem to be picking u...

James•8/26/23, 7:58 PM

If you are using

@cloudflare/next-on-pages

@cloudflare/next-on-pages

, the functions directory will not work as we generate our own

_worker.js

_worker.js

instead, and, as such, you should use Next.js Edge API routes instead.

JJames If you are using `@cloudflare/next-on-pages`, the functions directory will not w...

slagathor•8/26/23, 8:02 PM

got it. ty!

RRaindrops hello there! is there a repo with functions examples? I kinda want to understand...

Fizzy Kombucha•8/27/23, 3:31 AM

https://developers.cloudflare.com/pages/tutorials/build-an-api-with-pages-functions/
not a repo but detailed instructions for building one

Build an API for your front end using Pages Functions · Cloudflare ...

In this tutorial, you will build a full stack Pages application. Your application will contain:

sakuta•8/27/23, 4:38 PM

do functions run in front of the cache just as workers?

kianOP•8/27/23, 4:38 PM

Yup

kianOP•8/27/23, 4:39 PM

Well, Pages itself is a Worker so there isn’t really any origin cache in the first place - just the Cache API

Erisa•8/27/23, 5:56 PM

Static assets have their own internal cache

Erisa•8/27/23, 5:57 PM

dynamic responses from functions do not, so those need to use cache api

Asatsuki•8/28/23, 5:04 PM

has anyone gotten langchain to work on cloudflare pages? it says crypto.getHashes has not been implemented yetcrypto.getHashes has not been implemented yet when i try to deploy

Shivam•8/29/23, 11:19 AM

hello, can anyone help me with this issue?
functions

AAsatsuki has anyone gotten langchain to work on cloudflare pages? it says `crypto.getHash...

Vero•8/29/23, 3:24 PM

It should work using fetch()

VVero It should work using fetch()

Asatsuki•8/29/23, 4:36 PM

Thanks for the reply. Can you specify where I should use fetch()? the error occurs in deployment when i have this inside /server/api/query.ts (using nuxt 3):

import { OpenAI } from 'langchain/llms/openai';

export default defineEventHandler(async e => {
   const model = new OpenAI(); //OPENAI_API_KEY set in env
});

import { OpenAI } from 'langchain/llms/openai';

export default defineEventHandler(async e => {
   const model = new OpenAI(); //OPENAI_API_KEY set in env
});

Unsmart•8/29/23, 4:41 PM

I would assume both are exactly the same results just slightly different response

AAsatsuki Thanks for the reply. Can you specify where I should use fetch()? the error occu...

Vero•8/29/23, 5:04 PM

sorry, I've never used langchain, so can't really tell you specifically how to make it work

VVero sorry, I've never used langchain, so can't really tell you specifically how to m...

Asatsuki•8/29/23, 5:14 PM

okay thanks anyway!

Unsmart•8/29/23, 11:25 PM

are you getting errors?

Erisa•8/29/23, 11:59 PM

I would recommend contacting MailChannels support with as much detail as possible https://support.mailchannels.com/hc/en-us/requests/new

tozz•8/30/23, 4:11 PM

Just jumped on Pages and I am liking it so far, added a trivial function, setup route filtering etc. All is good, but I can't for the life of me figure out when I should use functions and when I should use workers. Functions are workers but with a different API and some file based routing sprinkled on top? When would you use a worker in a Pages/function deploy?

Ttozz Just jumped on Pages and I am liking it so far, added a trivial function, setup ...

Dahoom•8/30/23, 5:30 PM

If you want better analytics per worker then use workers, if you want to be able to specifically choose which billing method (bundled or unbundled) per api route then use workers

Dahoom•8/30/23, 5:32 PM

Pages is a little behind workers and currently works like a blanket system that I assume is mainly there to help streamline SSR, but you would get more fine grained control using a worker

DDahoom If you want better analytics per worker then use workers, if you want to be able...

tozz•8/30/23, 7:44 PM

All right, that makes sense, too bad workers doesn't have the nice GitHub-integration that pages has

Ttozz All right, that makes sense, too bad workers doesn't have the nice GitHub-integr...

Dahoom•8/31/23, 12:54 AM

It kind of does though, if you work on it locally you can deploy the worker with wrangler and I believe it will use the commit description that you last used on it. You can also then go to the dashboard and see that history and rollback to whatever deployment you had

DDahoom It kind of does though, if you work on it locally you can deploy the worker with...

tozz•8/31/23, 5:42 AM

Sure and that works well for a single dev, but if I had multiple people working on it and perhaps mulitple workers (I'm currently looking at having just one for now and do routing) I'd prefer everyone not having to deploy from their machines

tozz•8/31/23, 5:43 AM

But it's a minor thing really, for now I just want to get more clarity on when to use what

Dahoom•8/31/23, 7:34 AM

Apparently from what I've learnt it's ok to have 1 worker containing everything you need since it only really affects cold start times, and as long as it's warm it should be instant I think

Dahoom•8/31/23, 7:35 AM

Just make sure any new npm packages don't bloat your worker, I had some random packages I didn't even use much load entire 7MB json files into the worker

You can kind of do that like this... ```js for (const property in req) { console.log(`${property}

Similar Threads

Similar Threads

Similar Threads