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-static-tools

v1.5.2

Published

Tools for building grapqhl static sites with next.js

Downloads

29

Readme

next-static-tools

A toolkit for building graphql powered static sites with next.js

next-static-tools is not a static site generator, it is collection of utilities to make building static sites with next.js and graphQL easier. Here is an example of how it works.

Features

  • Write your own graphql type definitions and resolvers = Super flexible data layer
  • Query data with the amazing Apollo Client
  • Prefetch both your javascript components and data for instant page transitions
  • Service workers by default
  • Familiar next.js workflow

How does it work?

You provide a graphql schema and next-static-tools stands up a graphql server, during development you can query this server directly like a regular web app. However when you build your static site, we write out the queries and their results to JSON files and configure the client to fetch data from the served JSON instead of the graphql server. Which allows you to use Apollo in your in your next.js static websites :)

Why?

I built next-static-tools because I love the way graphql allows you to query arbitrary data in a uniform way. It's a powerful tool to have when building static sites where data often comes from random sources. I don't like how many static site generators rely on conventions to organise your data or abstract the data model behind plugins. With next-static-tools you control your data because you control your graphql schema, the rest is just regular Next.js.

NB: If you don't know graphql or don't want to learn, this tool isn't for you.

Usage:

yarn add react react-dom next next-static-tools
const yargs = require('yargs')
const next = require('next')
const { build, createServer } = require('next-static-tools')

yargs
  .version()
  .command('dev', 'run dev server', () => {
    const dev = process.env.node_env !== 'production'
    const app = next({ dev })

    const server = createServer(app)
    // add yo custom middleware
    server.get('/post/:id', (req, res) => {
      return app.render(req, res, '/post', {
        id: req.params.id
      })
    })

    server
      .start()
      .then(port => console.log(`server on http://localhost:${port}`))
      .catch(console.err)
  })
  .command('export', 'export static site', () => {
    // starts the grapql server
    // compiles next.js components
    // exports static site
    build()
      .then(() => 'Your static site is ready!')
      .then(() => process.exit())
      .catch(err => {
        console.log(err)
        process.exit(1)
      })
  }).argv

Sites built with next-static-tools:

If you feel something is missing, not clear or could be improved, please don't hesitate to open an issue in GitHub, I'll be happy to help.