Warning '@neondatabase/serverless' can only connect to remote Neon/Vercel Postgres/Supabase instances through a websocket, but it still works?

[waynesbrain]

What is the point of this warning when the migrations are working when using @neondatabase/serverless?

I was able to get rid of this warning for drizzle-kit by installing pg but I'd rather not do that, even as a dev dependency, if I can help it.

The warning (src) conflicts with the advice given when no driver is installed (src):

To connect to Postgres database - please install either of 'pg', 'postgres', '@neondatabase/serverless'...

Main question:

Can I simply ignore this warning, since my migration is still working and if so what are the ramifications?

See also:

• Warning '@neondatabase/serverless' can only connect to remote Neon/Vercel Postgres/Supabase instances through a websocket, but it still works? neondatabase/neon#12508
• https://www.answeroverflow.com/m/1238825489125081188
• https://discord.com/channels/1043890932593987624/1392145903690715177

[waynesbrain]

Also, looking at this line I can see that a websocket IS being used...

neonConfig.webSocketConstructor = ws;

[waynesbrain]

Based on my findings, I decided to ignore the warning and proceed with doing migrations without installing pg because I'm trying to keep my node_modules as slim as possible.

I guess that this warning is strictly informational.

If and when something stops working, I'll give an update.

[WilliamIsted]

📎

It looks like you're trying to resolve an issue with pg, would you like some help?

[waynesbrain]

Thanks @WilliamIsted but I have removed pg from the project and I have confirmed that it's been removed from node_modules as well as from my package-lock.json file.

My question is about why this warning shows, but now I think that I understand it now. I believe that it exists to let the developer know that drizzle-kit is about to use some WebSockets to connect in order to do the migration.

I think it's a pre-emptive warning to say "Hey, if anything goes wrong, make sure your DB is accessible via WebSockets!"