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

fluent-async-proxy

v0.1.1

Published

> Cool util for creating arbitrary async fluent APIs

Downloads

1

Readme

fluent-async-proxy

Cool util for creating arbitrary async fluent APIs

Imagine you'll want to create fluent APIs like below ✨

Of course - you can create chained objects/class instances (with load of boilerplate & some design restrictions) - but there seems to be easier & more powerful way with ES6 proxies.

There are pros & cons of meta-programming, arguably - it makes code harder to reason about (so use it responsibly).

My use case was auto-generating api clients, but it's kind of generic pattern for any path proxy.

Features

  • create arbitrary fluent APIs for async functions
  • delay callback execution till await/ start of promise chain
  • just few lines, no dependencies (more like idea than a project)
  • cjs/ esm/ typescript/ tested

Example

Paths segments are provided as array of tuples of propname and array of args arrays.

type Segments = Array<[Propname, ArgsArray[]]>
// or
type Segments = Array<[string, any[][]>

It's not super human readable, but (imho) incredibly handy to reduce/map/filter/validate/whatever

import { fluentAsyncProxy } from 'fluent-async-proxy'

// this handler does nothing
const handler = (paths: Segments) => {
  /* do smth */
}

const proxy = fluentAsyncProxy(handler)

const result = await proxy
  .users({ email: '[email protected]' })
  .posts()
  .first(3)
  .comments.withMetadata().literallyAnythingElse[2][3]

// paths poassed to handler
// [
//   ['users', [[{ email: '[email protected]' }]]],
//   ['posts', [[]]],
//   ['first', [[3]]],
//   ['comments', []],
//   ['withMetadata', [[]]],
//   ['literallyAnythingElse', []],
//   ['2', []],
//   ['3', []]
// ]

Installation


$ yarn add fluent-async-proxy

Another Example

import { fluentAsyncProxy } from 'fluent-async-proxy'

// this handler prints paths back to code, why not^^
const handler = async (paths: Segments) =>
  paths
    .map(
      ([prop, calls]) =>
        '.' +
        prop +
        (calls.length === 0
          ? ''
          : calls
              .map(args => `(${args.map(a => JSON.stringify(a)).join(', ')})`)
              .join(''))
    )
    .join('\n')

const client = fluentAsyncProxy(handler)

const comments = await client
  .users({ email: '[email protected]' })
  .posts.first(3)
  .comments.withMetadata()

// paths = [
//   ['users', [[{ email: '[email protected]' }]]],
//   ['posts', []],
//   ['first', [[3]]],
//   ['comments', []],
//   ['withMetadata', [[]]]
// ]

// result = `
//   .users({"email":"[email protected]"})
//   .posts
//   .first(3)
//   .comments
//   .withMetadata()
//   `

Unwrap

Before calling await or any of promise methods (then/catch/finally) the target of a proxy is only noop function.

To unwrap proxy to promise/ result immediately (to get call handler), but without awaiting - there is .UNWRAP trap.

const t = client.something()

// still a proxy
t instanceof Promise === false

// promise from callback handler
t.UNWRAP instanceof Promise === true