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

hashql

v0.5.1

Published

HashQL

Downloads

10

Readme

HashQL

Chuck Norris can access the DB from the UI.

This implementation consists of 3 pieces.

  • The Client module
  • The Build module
  • The Server module

The Client

The client is very simple and is the one you'll be using the most. To set it up you define which backends you want, and it returns a tagged template function to use for the queries. This allows you to easily integrate with any transport (fetch, WebSocket, XMLHttpRequest or a 🐦).

import HashQL from 'hashql'

const { sql } = HashQL('sql', query => 
  fetch('/hql', {
    method: 'POST',
    body: JSON.stringify(query)
  }).then(res => res.json())
)

await users = sql`select * from users`

The Build module

The job of the build module* is to replace all HashQL instances in the client code with their corresponding hashes, and to store the pair for lookup by the server (could be in a json file or database).

import HashQL from 'hashql/esbuild.js'

esbuild.build({
  ...,
  plugins: [
    HashQL({
      tags: ['sql'],
      output: queries => fs.writeFileSync(
        'hashql.json', 
        JSON.stringify(queries, null, 2)
      )
    })
  ]
})
  • Currently the build part is available as both a esbuild and rollup plugin, but it should be fairly simple to support other bundlers or have it as a completely standalone module to run by itself.

The Server module

The Server Module handles the incoming queries and then calls the handler functions to do the actual query and return the result. This is fairly simple to implement with most libraries. Here is a sample with Node and Postgres.js requests.

import HashQL from 'hashql/server.js'
import postgres from 'postgres'

const sql = postgres({ ... })

const hql = HashQL(queries, {
  
  sql: (query, input, context) => 
    sql.call(null, query, ...input),
  
  node: (query, input, context) =>
    eval(query.slice(1).reduce(
      (acc, x, i) => acc + JSON.stringify(input[i]) + x, 
      query[0])
    )

})

app.post('/hql', (req, res) => {
  hql(req.body, req.user)
    .then(x => res.end(x))
    .catch((err) => {
      res.statusCode = err.status
      res.end(err.message)
    })
})