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

next-rpc-ts

v0.1.1

Published

This is a library for

Downloads

4

Readme

Next JSON RPC

This is a library for

Getting started

Install the package via

npm i next-rpc-ts

or

yarn add next-rpc-ts

How to use next-rpc-ts

1. Create a router

// router.ts
import { createRouter } from 'next-rpc-ts'

export const router = createRouter().addRoute(
  'myFirstRoute',
  (x: string) => x.length
)

2. Export the routers api handler

// ~/pages/api/[...route].ts
import { router } from '~/router'

const handler = router.getApiHandler()

export default handler

Important: The name of the file has to correspond to the router configuration apiFileName field. More about configuration here

You can learn more about this type of api route in the nextjs docs.

3. Create the client side fetcher function

// fetcher.ts
import { createRouteFetcher } from 'next-rpc-ts'
import type { router } from '~/router'

export const fetcher = createRouteFetcher({
  baseUrl: 'http://localhost:3000',
})

You can learn more about the fetchers configuration here

4. Use the fetcher in a type-safe way

import { fetcher } from '~/fetcher'

// length = 6
const length = await fetcher('myFirstRoute', 'string')

// type error
await fetcher('myFirstRoute', 4)

Router Configuration

The router shares some common config options with the fetcher: config.ts.

You can find the jsdoc for the router configuration here.

Fetcher Configuration

The fetcher shares some common config options with the router: config.ts.

You can find the jsdoc for the fetcher configuration here.

How does this work?

Typescript makes it possible to preserve each individual routes function type assigned to the specific name.

By collecting all the routes and juggling around with their types we work out a few type connections, including but not limited to:

  • the parameter types for a route by name
  • the return type for a route by name
  • the context type by a functions return type
  • etc.

We can import the routers type to the client and into the createRouteFetcher function. The different routes are then combined into a function taking the name, the list of parameters and returning a promise holding the routes return value.