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

linopress

v0.0.1

Published

Static site generator with GUI, React components and JSON Schema

Downloads

3

Readme

Linopress

Linopress is a static site generator based on React components and JSON Schema with a local GUI to make editing easy.

⚠ Use only with a truckload of salt, this is just an exploration of the concepts and utterly rough around the edges.

Start a new project

To get started quickly, copy the files in /example to a new directory and install dependencies using npm install.

Edit

To start editing start up editing mode with npm start. This will fire up the frontend at localhost:3000 in your browser. You can now start using the editing interface at localhost:3000/editor.

All content changes will be persisted to your filesystem in content/. If you want to edit react components or add new ones, do this in your project folder in src/components/ and change the JSON schema for the editor in src/api/schema.json if needed.

Build

Run npm run build to build a statically deployable rendering of your website into build/.

TODO

  • Use schema.json from project folder
  • Make ports configurable
  • Editor can revert changes (using a temporary file that has to be explicitly commited)
  • I18N of content
  • Frontend uses websockets to listen for change messages instead of polling
  • Drop jdorn/json-editor in favor of mozilla-services/react-jsonschema-form once #52 is resolved