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

@jaris/core

v0.0.7

Published

> TODO: description

Downloads

3

Readme

@jaris/core

jaris is still in very early alpha, production usage is not recommended

Jaris. A 0 dependency, functional (phoenix) inspired, node / typescript web framework.

Installation

$ npm install -S @jaris/core

Usage

The core concept behind jaris is that the conn object gets passed through a series of functions (middleware), and the final resulting conn determines what is sent.

The conn object should never be mutated directly, only copied via spread (...conn), or modified using one of the conn helper functions provided.

A simple hello world would look like:

import server, { text } from '@jaris/core';

server([conn => text('Hello, world!', conn)]);

An example using multiple middleware would look like:

import server, { text } from '@jaris/core';

server([
  (conn) => ({
    ...conn,
    body: 'I will be overwritten',
  }),
  (conn) => text('Hello, world!', conn),
  (conn) => {
    console.log('I dont modify the connection at all, I just do some logging'),
    return conn;
  }
])

Since the conn object is simply modified to achieve a response, and all of the response helper functions provided by jaris are automatically curried, we can combine them using the pipe helper:

import server, { json, status, header } from '@jaris/core';
import { pipe } from '@jaris/util';

server([
  conn =>
    pipe(
      status(200),
      header('X-Custom', 'my value'),
      json({ ok: true }),
    )(conn),
]);

Which becomes even more useful when you start making re-usable responses

import server, { json, status, header } from '@jaris/core';
import { pipe } from '@jaris/util';

const formErrors = (errors: any) =>
  pipe(
    status(422),
    json({ errors }),
  );

server([
  conn =>
    formErrors({
      name: 'is required',
    })(conn),
]);

A simple request-time example:

import server, { header } from '@jaris/core';
import { pipe } from '@jaris/util';

const currentTimestamp = () => Math.round((new Date()).getTime() / 1000);

server([
  conn => header('X-Start-Time', `${currentTimestamp()}`, conn),
  conn => {
    // ...perform some relatively long task
    return conn;
  },
  conn => {
    const startTime = parseInt(conn.headers['X-Start-Time']);
    const endTime = currentTimestamp();

    return pipe(
      header('X-End-Time', `${endTime}`)
      header('X-Total-Time', `${endTime - startTime} seconds`)
    )(conn);
  }
]);