```js JSON.stringify(req, Object.getOwnPropertyNames(Object.getPrototypeOf(req)), '\t') ```

Kkian ```js JSON.stringify(req, Object.getOwnPropertyNames(Object.getPrototypeOf(req))...

T

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

Thanks, i will try to understand that ....

K

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

You'd be better off creating your own logging accessing each property as necessary

K

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

i.e

console.log({
  url: req.url,
  method: req.method,
  ...
});

console.log({
  url: req.url,
  method: req.method,
  ...
});

console.log({
  url: req.url,
  method: req.method,
  ...
});

console.log({
  url: req.url,
  method: req.method,
  ...
});

T

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

I am just experimenting with pages, and I wanted to check if there were any undocumented data in the context object. I don't have much experience with JS, and I was surprised that I couldn't list all the properties of this object, as is possible in others programming language like with vardump() in PHP, dir() vars() in python .... for example. Thank you, @kian.

K

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

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]}`);
}

K

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()

Object.keys()

Object.keys() or

console.log()

console.log()

console.log()

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

Object.getOwnPropertyNames()

Object.getOwnPropertyNames()

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...

K

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

K

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

T

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

Very interesting information!

Original message was deleted

J

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

S

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.

S

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

that makes sense...thanks!

X

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)

J

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

I would guess one of your dependencies got updated

X

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

@cherryjimbo No packages have been updated / removed / added

J

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

^1.0.0

^1.0.0 (note the

^

^), then any version compatible with

1.0.0

1.0.0

1.0.0

1.0.0 could be installed

J

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.

J

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

S

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>

<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?

S

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

The contents of my

functions/getFeed.js

functions/getFeed.js

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!")
}

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

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

And it's still returning 404

S

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...

J

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

If you are using

@cloudflare/next-on-pages

@cloudflare/next-on-pages

@cloudflare/next-on-pages

@cloudflare/next-on-pages, the functions directory will not work as we generate our own

_worker.js

_worker.js

_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...

S

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...

F

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:

S

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

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

K

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

Yup

K

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

E

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

Static assets have their own internal cache

E

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

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

A

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

has anyone gotten langchain to work on cloudflare pages? it says

crypto.getHashes has not been implemented yet

crypto.getHashes has not been implemented yet

crypto.getHashes has not been implemented yet

crypto.getHashes has not been implemented yet when i try to deploy

S

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...

V

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

It should work using fetch()

VVero It should work using fetch()

A

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
});

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
});

U

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...

V

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...

A

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

okay thanks anyway!

U

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

are you getting errors?

E

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

T

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 ...

D

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

D

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...

T

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

```js JSON.stringify(req, Object.getOwnPropertyNames(Object.getPrototypeOf(req)), '\t') ```

Similar Threads

Similar Threads

Similar Threads