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-ts-routes

v0.1.10

Published

A way to have fully typed routes in next, without all the complexity of tRPC.

Downloads

4

Readme

Typed Routes

A way to have fully typed routes in next, without all the complexity of tRPC.

This is more for super minimal use cases, where you don't need the full functionality of tRPC.

Installation


npm install next-ts-routes

yarn install next-ts-routes

pnpm install next-ts-routes

Usage

This is an example of how to use next-ts-routes

Add the next wrapper

// next.config.js
const withNextTsRoutes = require('next-ts-routes/withNextTsRoutes')

module.exports = withNextTsRoutes({})
// next.config.mjs
import { env } from "./src/env/server.mjs";
import { withNextTsRoutes } from 'next-ts-routes/withNextTsRoutes';

/**
 * Don't be scared of the generics here.
 * All they do is to give us autocompletion when using this.
 *
 * @template {import('next').NextConfig} T
 * @param {T} config - A generic parameter that flows through to the return type
 * @constraint {{import('next').NextConfig}}
 */
function defineNextConfig(config) {
  return withNextTsRoutes(config);
}

export default defineNextConfig({
});

Set HOST env variables

You have to set HOST or NEXT_PUBLIC_HOST in your environment variables for next-ts-routes to work.

// .env.local
HOST=http://localhost:3000

For the time being this is a hacky way to achieve this, will ideally fine a better way in the future.

// next.config.js
const withNextTsRoutes = require('next-ts-routes/withNextTsRoutes')

module.exports = withNextTsRoutes({}, {
  fs: false
})

Basic Usage

You can see an example with typescript intellisense here - https://stackblitz.com/edit/typescript-qbv1tp?file=index.ts

// api/clip.ts
import { route } from "next-ts-routes";

const { handler, get, post } = route("api/clip", {
  ctx: async () => {
    const Redis = (await import("@upstash/redis")).Redis;

    const redis = new Redis();

    return { redis };
  },
  GET: async ({}, { ctx }) => {
    return ctx.redis.get("clip") as Promise<string | undefined>;
  },
  POST: async ({ input }: { input: { text: string } }, { ctx }) => {
    return ctx.redis.set("clip", input.text);
  },
});

export const getClip = get;
export const postClip = post;

export default handler;

Note: As this file is directly imported in the browser, you cannot use any nodejs specific imports, like fs or path globally. You should dynamically import them and then use them.

Now you can import the getClip and postClip functions and use them in your app.

// pages/index.tsx
import { getClip, postClip } from '../api/clip';

export default function Home() {
  const [clip, setClip] = useState<string | undefined>(undefined);

  useEffect(() => {
    getClip().then(setClip);
  }, []);

  return (
    <div>
      <h1>Clip</h1>
      <p>{clip}</p>
      <form
        onSubmit={async (e) => {
          e.preventDefault();
          const text = e.currentTarget.elements[0].value;
          await postClip({ text });
          setClip(text);
        }}
      >
        <input type="text" />
        <button type="submit">Set</button>
      </form>
    </div>
  );
}

This can totally be used with swr or react-query as well for nice hooks, will write some docs for this later