Skip to content

Update readme text slightly #3637

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.

Sign up for GitHub

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

Merged
brianc merged 2 commits into from
Mar 6, 2026
+5 −5
Merged

Update readme text slightly #3637

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ac66806
Update readme text slightly
brianc Mar 6, 2026
35ad992
Better words
brianc Mar 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ When you open an issue please provide:
- version of Postgres
- smallest possible snippet of code to reproduce the problem

You can also follow me [@briancarlson](https://twitter.com/briancarlson) if that's your thing. I try to always announce noteworthy changes & developments with node-postgres on Twitter.
You can also follow me [@brianc](https://bsky.app/profile/brianc.bsky.social) on bluesky if that's your thing for updates on node-postgres with nearly zero non node-postgres content. My old twitter/x account is no longer used.

## Sponsorship :two_hearts:

Expand Down Expand Up @@ -87,11 +87,11 @@ If your change involves breaking backwards compatibility please please point tha
### Setting up for local development

1. Clone the repo
2. Ensure you have installed libpq-dev in your system.
2. Ensure you have installed libpq-dev in your system (the native bindings are built in the test process)
3. From your workspace root run `yarn` and then `yarn lerna bootstrap`
4. Ensure you have a PostgreSQL instance running with SSL enabled and an empty database for tests
5. Ensure you have the proper environment variables configured for connecting to the instance
6. Run `yarn test` to run all the tests
4. Ensure you have a PostgreSQL instance running with SSL enabled and an empty database for tests. _note: you can skip the tests requring SSL by setting the environment variable `PGTESTNOSSL=1` if you're not changing any SSL related code_.
5. Ensure you have the proper environment variables configured for connecting to your postgres instance. Using the standard `PG*` environment variables like `PGUSER` and `PGPASSWORD` etc...
6. Run `yarn test` to run all the tests.

## Troubleshooting and FAQ

Expand Down