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

grokodile

v1.0.0

Published

get your code/website publicly accessible while developing

Downloads

3

Readme

:crocodile: grokodile :crocodile:

get your code/website publicly accessible while developing

install / setup

to run in your project:

$ npx grokodile

or you can install it globally and run it quickly whenever you want:

$ npm install -g grokodile
$ grokodile

the default config runs a local dev server on port 3000 and builds your project with npm run build. it assumes your build script puts files to be served in the directory ./build.

you can override any of these settings by creating a config file for your project by creating a .grokodile.json file.

(optionally, you could name the file anything and tell grokodile with the --config <file> option.)

config options

| option | description | default | |--------|-------------|---------| |port|the port the local dev server will listen on|3000| |build|the command grokodile should run to build your project|npm run build| |path|the path to serve (where the built files are)|./dist| |httpServer|enable/disable the local dev http server|true|

sample config file

this sample config file uses parcel for the builder and doesn't enable grokodile's built-in http server because parcel automatically starts one on port 1234 (note we specify the port even though the http server is disabled, because it is needed for ngrok).

{
  "build": "parcel",
  "httpServer": false, 
  "port": 1234
}

what's happening

  • start a local http server that serves static files
  • connect ngrok so the server is accessible on the internet
  • run your build script (which should be set up to watch files and rebuild)

license

MIT