-
Notifications
You must be signed in to change notification settings - Fork 22
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
Moving this module into node-postgres monorepo #37
Comments
Hey I'm planning on starting on this today if y'all don't have objections?! I have a couple things coming up I'd like to include here & putting this in the monorepo would make it easier! |
PR here! brianc/node-postgres#2184 Gonna ping you on the PR so we can discuss publish access or npm package ownership transfer. |
Now that brianc/node-postgres#2184 has landed, we should direct people to that repo. I believe the best option is to archive this repo and update the README with instructions to visit https://github.com/brianc/node-postgres @louiemontes let me know what you think |
Just wanted to thank y'all for your help w/ this. I'm releasing a new Please don't hesitate to come contribute on the main repo too - you're all always welcome! ❤️ |
Now that #41 is merged, what do you think about archiving this repository (as suggested in the original post)? |
Please see the discussion here: brianc/node-postgres#2105 (comment)
If that does happen, then I suggest we archive this repo and point people to node-postgres. Old releases will continue to function and new development will be in lock-step with node-postgres.
The text was updated successfully, but these errors were encountered: