Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that this is not node-postgres (on npm)? #3314

Open
mmkal opened this issue Sep 18, 2024 · 0 comments · May be fixed by #3339
Open

Clarify that this is not node-postgres (on npm)? #3314

mmkal opened this issue Sep 18, 2024 · 0 comments · May be fixed by #3339

Comments

@mmkal
Copy link

mmkal commented Sep 18, 2024

Hi - I just created fuxingZhang/postgres#2 because for the Nth time I accidentally went to the wrong npm package.

I wonder if this library should just stop referring to itself as node-postgres, since the way users install is npm install pg, and not npm install node-postgres. I know the website is node-postgres.com but uhh maybe that could eventually not be the case either.

DavideViolante added a commit to DavideViolante/node-postgres that referenced this issue Oct 31, 2024
DavideViolante added a commit to DavideViolante/node-postgres that referenced this issue Oct 31, 2024
@DavideViolante DavideViolante linked a pull request Oct 31, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant