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

@ryze-digital/create-website

v1.0.0-beta.1

Published

Sets up build tools and default folder structure

Downloads

129

Readme

RYZE Digital Project Starter Kit

Run linter(s) workflow status

Usage

Open the folder in which you want to set up a new project. In Ecoma projects (for example) this is /public/project/frontend. The folder needs to be empty. Run the following script and replace @namespace/project-name with the name of your project.

npm init @ryze-digital/website@latest @namespace/project-name

Options

Change output directory

By default, the output directory is /build. If build files need to be located under a different path, you can add a third parameter to the call from above:

npm init @ryze-digital/website@latest @namespace/project-name ../../public/dist

The path has to be relative to the folder in which you run the command.

Toubleshooting

If you use a path outside the folder in which you run the command, it can happen that the pre-production script throws the following error:

Warning: Cannot delete files outside the current working directory. Use --force to continue.

To fix this, you can set deleteOriginals to false for the cacheBust task inside Gruntfile.js. Please note that in this case the unhashed build files will remain in the output directory.

Loglevel

Loglevel can be changed to see more detail output during installation. By default, loglevel is silent. Allowed values are error, warn, info, verbose and silly.

npm init @ryze-digital/website@latest @namespace/project-name --loglevel error