I'm using Remix with Pages, and I have a few issues. When I use the `pg` package, I get the errors

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

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

So I added in some

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

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,

Elliot HespOP•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...

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.

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

Elliot HespOP•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

Elliot HespOP•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

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

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.

Elliot HespOP•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

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

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

nodejs_compat

nodejs_compat

and

node_compat

node_compat

are confusingly very different things

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

node_compat

node_compat

is a set of polyfills which is what

pg

pg

wants

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

nodejs_compat

nodejs_compat

are some

node:

node:

modules made available at runtime

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

Well TIL I didn't even notice that

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

pages dev

pages dev

supports

--node-compat

--node-compat

but

pages deploy

pages deploy

doesn't

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

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

Elliot HespOP•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

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

Elliot HespOP•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

Elliot HespOP•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...

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!

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

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

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

Thanks, really appriciate it

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

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

Yeah, it isn’t a compatibility flag

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

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

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

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

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

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

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

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

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

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

just asking how to do that

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

or perhaps i am not understanding your response @Hello, I’m Allie! ?

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

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

As far as documented APIs go, you can create a project via the API, but you cannot connect it to a Github repository.

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

is that because it's not possible or because it's just not documented?

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

e.g. d1 apis aren't documented but also exist

Aag_dubs is that because it's not possible or because it's just not documented?

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

You can do whatever the Dashboard does to create a project

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

Though I definitely wouldn't count on them being stable enough to rely on

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

that's ok for us imo

HHello, I’m Allie!You can do whatever the Dashboard does to create a project

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

is this consumable in a form that isn't the browser inspector by chance?

Aag_dubs is this consumable in a form that isn't the browser inspector by chance?

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

Wdym?

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

i just mean has someone else done this and kinda sketch how to do it

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

instead of me going in and figuring it out

Aag_dubs i just mean has someone else done this and kinda sketch how to do it

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

I don't think so. If you don't want to inspect the Network tab directly, then you would have to reverse the Dashboard browser bundle, which would take a while.

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

is this something that is facilitated better by the platforms program?

Aag_dubs is this something that is facilitated better by the platforms program?

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

Maybe? It has more API-support, but no Github/Gitlab support at all

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

nods

// 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,

I'm using Remix with Pages, and I have a few issues. When I use the `pg` package, I get the errors

Similar Threads

Similar Threads

Similar Threads