which means if we write simple html page, we don't need to do anything? so if we use anything like

Nnew2di5cord which means if we write simple html page, we don't need to do anything? so if w...

C

chientrm.com•8/15/23, 7:38 PM

I mean if you use framework, they have the part that handle cache-control.

C

chientrm.com•8/15/23, 7:38 PM

if u do on your own, you gotta set that header by yourself.

N

new2di5cordOP•8/15/23, 7:41 PM

the problem is I use WordPress plugin to generate static site, which is not common framework. I guess need to swith to hugo or next framework for next project.

U

Unsmart•8/15/23, 7:50 PM

Static content is perfect for pages. The framework does not control the cache when it is static pages.

E

Erisa•8/15/23, 8:54 PM

Pages is already distributed and already has its own cache, you don't need to change anything

N

new2di5cordOP•8/15/23, 9:20 PM

cool. Thank you all for confirm and idea for the framework solutions.

G

Garnaph•8/16/23, 11:03 AM

Hi all. I've posted in pages-help but thought I'd quickly ask here as well : is there any way to debug when you get an error message referencing minified js output? [This is for a nuxt3 pages app]

12:46:06.565    Error: Failed to publish your Function. Got error: Uncaught TypeError: Cannot read properties of undefined (reading 'exports')
  at functionsWorker-0.8391131841286965.js:21419:92

12:46:06.565    Error: Failed to publish your Function. Got error: Uncaught TypeError: Cannot read properties of undefined (reading 'exports')
  at functionsWorker-0.8391131841286965.js:21419:92

12:46:06.565    Error: Failed to publish your Function. Got error: Uncaught TypeError: Cannot read properties of undefined (reading 'exports')
  at functionsWorker-0.8391131841286965.js:21419:92

12:46:06.565    Error: Failed to publish your Function. Got error: Uncaught TypeError: Cannot read properties of undefined (reading 'exports')
  at functionsWorker-0.8391131841286965.js:21419:92

G

Garnaph•8/16/23, 11:04 AM

This has been driving me insane, so any help would be greatly appreciated

G

Garnaph•8/16/23, 11:05 AM

I get a similar error when trying to debug locally using wrangler :

service core:user:worker: Uncaught TypeError: Cannot read properties of undefined (reading 'exports')
  at bh25zprwrab.js:21509:92

service core:user:worker: Uncaught TypeError: Cannot read properties of undefined (reading 'exports')
  at bh25zprwrab.js:21509:92

service core:user:worker: Uncaught TypeError: Cannot read properties of undefined (reading 'exports')
  at bh25zprwrab.js:21509:92

service core:user:worker: Uncaught TypeError: Cannot read properties of undefined (reading 'exports')
  at bh25zprwrab.js:21509:92

G

Garnaph•8/16/23, 11:05 AM

I can never track down the location of this file [bh25zprwrab.js in this case] so not even sure where to start.

C

Christopher Pecoraro, MBA•8/16/23, 4:05 PM

Hi Pages team! It's been a while since I've checked in, but is there now a way to cache data between builds? We need this for Gatsby.

F

Fernando Dilland•8/16/23, 6:45 PM

It would not be a good idea for CF Pages to have by default hotlinking prevention? To prevent abuse of CF resources

E

Elliot Hesp•8/17/23, 8:54 AM

Is it not possible to use the pg package with Pages? This is for Workers https://developers.cloudflare.com/workers/tutorials/postgres/ but doesn't work in Pages (dev at least)

Connect to a PostgreSQL database with Cloudflare Workers · Cloudfla...

In this tutorial, you will learn how to create a Cloudflare Workers application and connect it to a PostgreSQL database using TCP Sockets. The Workers …

K

kian•8/17/23, 9:05 AM

Workers & Pages Functions are the same thing, Functions is just a wrapper around it - what isn’t working specifically?

E

Elliot Hesp•8/17/23, 9:27 AM

I'm using Remix with Pages, and I have a few issues.

When I use the

pg

pg

package, I get the errors:

 [ERROR] Could not resolve "dns"ng --force Recommended protections disabled.

    node_modules/pg/lib/connection-parameters.js:3:18:
      3 │ var dns = require('dns')
        ╵                   ~~~~~

  The package "dns" 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.


✘ [ERROR] Could not resolve "net"

    node_modules/pg/lib/connection.js:3:18:
      3 │ var net = require('net')
        ╵                   ~~~~~

  The package "net" 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.


✘ [ERROR] Could not resolve "net"

etc...

 [ERROR] Could not resolve "dns"ng --force Recommended protections disabled.

    node_modules/pg/lib/connection-parameters.js:3:18:
      3 │ var dns = require('dns')
        ╵                   ~~~~~

  The package "dns" 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.


✘ [ERROR] Could not resolve "net"

    node_modules/pg/lib/connection.js:3:18:
      3 │ var net = require('net')
        ╵                   ~~~~~

  The package "net" 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.


✘ [ERROR] Could not resolve "net"

etc...

 [ERROR] Could not resolve "dns"ng --force Recommended protections disabled.

    node_modules/pg/lib/connection-parameters.js:3:18:
      3 │ var dns = require('dns')
        ╵                   ~~~~~

  The package "dns" 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.


✘ [ERROR] Could not resolve "net"

    node_modules/pg/lib/connection.js:3:18:
      3 │ var net = require('net')
        ╵                   ~~~~~

  The package "net" 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.


✘ [ERROR] Could not resolve "net"

etc...

 [ERROR] Could not resolve "dns"ng --force Recommended protections disabled.

    node_modules/pg/lib/connection-parameters.js:3:18:
      3 │ var dns = require('dns')
        ╵                   ~~~~~

  The package "dns" 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.


✘ [ERROR] Could not resolve "net"

    node_modules/pg/lib/connection.js:3:18:
      3 │ var net = require('net')
        ╵                   ~~~~~

  The package "net" 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.


✘ [ERROR] Could not resolve "net"

etc...

E

Elliot Hesp•8/17/23, 9:27 AM

So I added in some

serverNodeBuiltinsPolyfill

serverNodeBuiltinsPolyfill

serverNodeBuiltinsPolyfill

serverNodeBuiltinsPolyfill (https://remix.run/docs/en/1.19.3/file-conventions/remix-config#servernodebuiltinspolyfill), which got around those issues, but then I get:

ReferenceError: process is not defined

ReferenceError: process is not defined

ReferenceError: process is not defined

ReferenceError: process is not defined

Which comes from the compiled:

// node_modules/pg/lib/defaults.js
var require_defaults = __commonJS({
  "node_modules/pg/lib/defaults.js"(exports6, module) {
    "use strict";
    module.exports = {
      // database host. defaults to localhost
      host: "localhost",
      // database user's name
      user: process.platform === "win32" ? process.env.USERNAME : process.env.USER,

// node_modules/pg/lib/defaults.js
var require_defaults = __commonJS({
  "node_modules/pg/lib/defaults.js"(exports6, module) {
    "use strict";
    module.exports = {
      // database host. defaults to localhost
      host: "localhost",
      // database user's name
      user: process.platform === "win32" ? process.env.USERNAME : process.env.USER,

// node_modules/pg/lib/defaults.js
var require_defaults = __commonJS({
  "node_modules/pg/lib/defaults.js"(exports6, module) {
    "use strict";
    module.exports = {
      // database host. defaults to localhost
      host: "localhost",
      // database user's name
      user: process.platform === "win32" ? process.env.USERNAME : process.env.USER,

// node_modules/pg/lib/defaults.js
var require_defaults = __commonJS({
  "node_modules/pg/lib/defaults.js"(exports6, module) {
    "use strict";
    module.exports = {
      // database host. defaults to localhost
      host: "localhost",
      // database user's name
      user: process.platform === "win32" ? process.env.USERNAME : process.env.USER,

E

Elliot Hesp•8/17/23, 9:29 AM

This stuff confuses me - I guess it's some issue with how Remix is bundling the code and what the cf runtime looks for or something

EElliot Hesp I'm using Remix with Pages, and I have a few issues. When I use the `pg` packa...

C

carter•8/17/23, 9:37 AM

Pages runs on the edge (cf's worker runtime), so a lot of things, packages, features that node provides won't be available.

If you're interested, some serverless hosts like: neon, vercel, supabase, planetscale, turso, cloudflare d1 all have libraries for interacting with their own databases on the edge. They kind of cheat, though, by using fetch requests to their api or some platform-specific tech rather than establishing a database connection. which makes the libraries proprietary (I think) to their provider.

C

carter•8/17/23, 9:39 AM

I'm not completely sure if there's a way to connect to pg directly from the edge, as I've just learned this stuff recently, but if you're content with using a serverless-compatable database, those are some good database driver options.

Ccarter I'm not completely sure if there's a way to connect to pg directly from the edge...

E

Elliot Hesp•8/17/23, 9:46 AM

Thanks - my understanding is Cloudflare now suppports TCP connections. I was hoping to use Drizzle to connect directly to Supabase (https://orm.drizzle.team/docs/installation-and-db-connection/postgresql/supabase

scroll to bottom) which suggests you can directly connect directly

E

Elliot Hesp•8/17/23, 9:47 AM

My issue with using the Supabase client is that it's HTTP like you said, I can't use transactions which is pretty much a requirement

K

kian•8/17/23, 9:50 AM

The

pg

pg

library on Workers requires

node_compat

node_compat

which I don't think you can enable on Pages

EElliot Hesp My issue with using the Supabase client is that it's HTTP like you said, I can't...

C

carter•8/17/23, 10:01 AM

Unfortunate that pages can't run node_compat. If you're needing transactions but still want to use the supabase database for sure, neon's serverless driver is able to run on any postgres database, as long as you run their websocket proxy for your edge clients.

E

Elliot Hesp•8/17/23, 10:13 AM

@kian Ah I have been running

wrangler pages dev ./public --compatibility-flags=nodejs_compat

wrangler pages dev ./public --compatibility-flags=nodejs_compat

wrangler pages dev ./public --compatibility-flags=nodejs_compat

wrangler pages dev ./public --compatibility-flags=nodejs_compat

although, in the dashboard for pages it does allow you to set that?

K

kian•8/17/23, 10:16 AM

nodejs_compat

nodejs_compat

and

node_compat

node_compat

are confusingly very different things

K

kian•8/17/23, 10:16 AM

node_compat

node_compat

is a set of polyfills which is what

pg

pg

wants

K

kian•8/17/23, 10:16 AM

nodejs_compat

nodejs_compat

are some

node:

node:

modules made available at runtime

E

Elliot Hesp•8/17/23, 10:22 AM

Well TIL I didn't even notice that

K

kian•8/17/23, 10:26 AM

pages dev

pages dev

supports

--node-compat

--node-compat

but

pages deploy

pages deploy

pages deploy

pages deploy doesn't

K

kian•8/17/23, 10:26 AM

so uh, I don't think it's usable in production

E

Elliot Hesp•8/17/23, 10:28 AM

I get

service core:user:worker: No such compatibility flag: node_compat

service core:user:worker: No such compatibility flag: node_compat

service core:user:worker: No such compatibility flag: node_compat

service core:user:worker: No such compatibility flag: node_compat

Ccarter Unfortunate that pages can't run node_compat. If you're needing transactions but...

E

Elliot Hesp•8/17/23, 10:34 AM

I'm not requring supabase, the main thing is being able to run transactions (via code) from Pages on a database:

So any SQL DB would be ok, I'm just trying to connect at the moment

I've been using Prisma which is great, but their data proxy reguarly hangs, and their support is slow and not helpful

E

Elliot Hesp•8/17/23, 10:35 AM

I either get cold starts (on their service) or timeouts

EElliot Hesp I'm not requring supabase, the main thing is being able to run transactions (via...

C

carter•8/17/23, 10:40 AM

I see, I'm about to head to bed, but I was googling to learn more about the different drivers just now and it seems like neon's driver in drizzle would be the most seamless switch for you. Neon's driver uses websockets as an alternative to native pooling or http, which means transactions & edge compatability ! Haven't used it before but they seem to be making lots of people happy, and were super nice with their pre-launch contact so I'd say give it your best shot!

C

carter•8/17/23, 10:40 AM

Can't wait to see how it turns out for you

E

Elliot Hesp•8/17/23, 10:54 AM

Thanks, really appriciate it

EElliot Hesp I get `service core:user:worker: No such compatibility flag: node_compat`

K

kian•8/17/23, 11:21 AM

Yeah, it isn’t a compatibility flag

K

kian•8/17/23, 11:21 AM

It’s a separate wrangler feature that Pages doesn’t support

Mmaxsb0261 hey I got told you shouldn't need page rules with cloudflare pages but looking a...

H

Hello, I’m Allie!•8/17/23, 12:30 PM

Because Pages uses its own cache which afaik doesn’t show up in Cache Analytics

Mmaxsb0261 thanks <@459755459117711362> if we use normal rules as well what kind of issues ...

H

Hello, I’m Allie!•8/17/23, 3:02 PM

It may make it slower for Pages to update after a new deploy occurs

A

ag_dubs•8/17/23, 3:22 PM

not entirely sure how to ask this question, but i'm generating pages projects via API and it is not clear to me how i connect a pages project to a github repo

there is a source key, but there's no docs on how to use it

A

ag_dubs•8/17/23, 3:24 PM

i've taken a look at how wrangler does it, looks like it's using a short sha- but if so, still not clear how that is associated with a github origin/repo

Aag_dubs i've taken a look at how wrangler does it, looks like it's using a short sha- bu...

H

Hello, I’m Allie!•8/17/23, 3:25 PM

Once a project is created, then you cannot attach it to a GitHub/GitLab repo. You have to create a new project, then connect it there

A

ag_dubs•8/17/23, 3:27 PM

so i am trying to create a project, attached to a github repo, via the API

which means if we write simple html page, we don't need to do anything? so if we use anything like

Similar Threads

Similar Threads

Similar Threads