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

@elliestudios/scripts

v0.2.0

Published

These are some scripts that I use to make websites a bit quicker.

Downloads

89

Readme

Website Scripts

These are some scripts that I use to make websites a bit quicker.

envgen

Generates .env files super quick, for multiple environments, based on a .env.example file.

.env.example example

#@ string
#@ reflect(service = web): NEXT_PUBLIC
#@ reflect(service = cms): PAYLOAD_PUBLIC
#@ env: dev, prod
#@ ask
SITE_NAME="The sites name"

#@ secret
#@ service: cms
#@ env: dev, prod
PAYLOAD_SECRET="The Payload CMS secret"

#@ port
#@ service: cms
#@ env: dev
CMS_PORT="The port the CMS will use"

#@ url
#@ service: cms
#@ default: http://localhost:${CMS_PORT}
#@ reflect(service = web): NEXT_PUBLIC
#@ env: dev, prod
#@ ask: prod
CMS_URL="The base URL for the CMS"

#@ url
#@ default: http://localhost:3000
#@ reflect(service = web): NEXT_PUBLIC
#@ reflect(service = cms): PAYLOAD_PUBLIC
#@ env: dev, prod
#@ ask: prod
WEB_URL="The base URL for the web"

Basically, any valid .env.example is a valid template for envgen, but using #@ comments, you can tell the tool how to process the environment variables and generate values. For the example above, when running deno run -A https://esm.sh/gh/elliestudios/scripts/envgen/mod.ts gen .env.example -env dev -service web, you would get prompted for the value of SITE_NAME, a free port would be used for CMS_PORT, CMS_URL would be inferred, WEB_URL would be the default localhost url but only NEXT_PUBLIC_SITE_NAME, NEXT_PUBLIC_CMS_URL and NEXT_PUBLIC_WEB_URL would actually be included in the final output.

This way, new .env files can be generated super quick with included documentation as to how variables are supposed to be utilized.

assetgen

Generates React components, CSS variables, favicons and more based off a colors.json and source-*.svg files. Simply run deno run -A https://esm.sh/gh/elliestudios/scripts/assetgen/mod.ts -i assets-folder and get a directory with the processed files.

License

MIT