npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

pg-funky

v2.1.3

Published

From a security standpoint, I prefer interacting with PostgreSQL only with functions from my applications. So, I made it easy. Also, I always returned JSON objects for ease of use with web projects. So that's what you get here.

Downloads

12

Readme

PG Funky

From a security standpoint, I prefer interacting with PostgreSQL only with functions from my applications. So, I made it easy. Also, I always let the server do the work, then return JSON. So, you always get back JSON.

Usage

//==================== funky.js
const { PGFunky } = require('pg-funky');

let config = {
  host: 'myPostgresHost', //required - Host of the postgres database
  port: 5432, //optional - port to connect to. Default: 5432
  user: 'theUser', //required - user to connect with
  password: 'thePassword', //required - password for the user
  database: 'theDatabase', //required - database to connect to
  application_name: 'pg-funky', //optional - Name of the application. Default pg-funky
  idleTimeoutMillis: 0, //optional - time before a client removes itself from the pool. Default 0 = Never
  max: 10 //optional - maximum number of clients allowed in the pool. Default: 10
  ssl: false, //optional - If using ssl use {rejectUnauthorized: true} when using legit certs. Default: false
}

let funky = new PGFunky(config);


funk.start().then(()=>{
  console.log('Systsem is ready')
}).catch((e)=>{
  console.log('System failed:', e.message)
})

module.exports = funky

//==================== user-model.js
const funky = require('./funky')

const funky = require('./funky');

//type is optional, but if you are using method overloading on the postgres side you will need it
funky.execute('identities.get_user', [{ type: 'bigint', value: 1 }]).then((user) => {
  console.log(user);
});