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

atomic-api

v0.0.1

Published

**WARNING: This is Work-In-Progress!**

Downloads

2

Readme

Atomic API

WARNING: This is Work-In-Progress!

Use atomic-router as your router for Node.js backend

Install

npm install atomic-router atomic-api

Usage

  1. Create API controls
// @/shared/api
import { createApiControls } from "atomic-api";

// Returns { $method, $response } stores
export const apiControls = createApiControls();
  1. Create API route
// @/routes/post
import { createApiRoute } from "atomic-api";

import { apiControls } from "@/shared/api";

export type PostParams = {
  postId: string;
};

export const post = createApiRoute({
  controls: apiControls,
  api: {
    GET: ({ params }) => {
      return {
        id: params.postId,
        title: "Some Post",
      };
    },
  },
});

// `createApiRoute` returns this
post.route; // Route created by atomic-router
post.api.GET; // Effect<RouteParamsAndQuery<PostParams>, ...>
  1. Create a router
// @/app/router
import { createHistoryRouter } from "atomic-router";

import { post } from "@/routes/post";

export const routes = [{ path: "/posts/:postId", route: post.route }];

export const router = createHistoryRouter({
  routes,
});
  1. Create a server
// @/app/server
import { createHttpServer } from "atomic-api";

import { router } from "@/app/router";
import { apiControls } from "@/shared/api";

export const server = createHttpServer({
  router,
  controls: apiControls,
});

server.listen(3002);

How does it work?

  1. createHttpServer starts a server (via http.createServer)
  2. On each request:
    2.1. Trigger fork and creates a new scope 2.2. Store req.method in apiControls.$method 2.3. Create history instance and pushes req.url to it 2.4. Trigger router.setHistory with a passed scope 2.5. Router opens matched route 2.6. Check apiControls.$method and open matching sub-route (created by chainRoute) 2.7. Trigger effect and wait until it's finished 2.8. effect.doneData writes its response to apiControls.$response 2.9. Trigger res.send with apiControls.$response data

TODO:

  • [ ] Actually send response
  • [ ] Pass req/res instance to effects
  • [ ] Redirects