fix(connectors): update import to work with esm

[amandesai01]

🔗 Linked issue

Resolves #62

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Updated import statement for "pg" so that is works well with *.mjs files.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[amandesai01]

can we merge this? need this in a project.

[pi0]

sorry for delay but i need further testing to see either prefer this or import * as syntax (i understand it fixes nitro builds)

in the meantime i suggest to use pnpm patch.

[joerosenthal]

Any updates on this? Currently having issues with using pg in a nuxt3 project on the nitro side of things—same failure to import: "The requested module 'pg' does not provide an export named 'Client'"

[BlueBazze]

Any updates on this? Currently having issues with using pg in a nuxt3 project on the nitro side of things—same failure to import: "The requested module 'pg' does not provide an export named 'Client'"

Based on what I've seen and read.
Yes, pg is unusable until this is fixed. But keep in mind that it is an experimental feature, so it probably has a low priority.
Especially since they are in the middle of releasing nitro 3.0, and nuxt is working on nuxt 4.0
Nitro 3.0 was planned for the middle of june or july, so pi0 is likely working that.

[TimvdEijnden]

I also wanted to use db0 with postgres, but this is blocking me. @pi0 can you help a fellow Passionate Person 😉