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

wes-cli

v3.0.1

Published

CLI for all things Wes

Downloads

41

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

wessouzawessouza

Keywords

boilerplatecliconfig

Readme

wes-cli

CI Tests status badge npm version

Collection of CLI commands that make my life easier, such as maintaining configuration files across different projects. It might help you too!

Commands

wes install

Reads wes-config.json file in the current directory and installs files related to all dependencies. All files are added to the .gitignore file because they are generated and copied from the package itself.

All configurations are merged with each other, allowing multiple packages to change the same configuration depending on their need. The current logic is extremely simplistic (plain text files are appended, JSON files are deeply merged, yarn.lock files are regenerated). Files which can't be merged can be used, but only one version should exist, as another will generate a conflict.

Local overrides to configured files should be added to .wes-defaults/local, which will be merged last to take precedence for potential overrides.

This project is built using itself, so you can peek at wes-config.json and .wes-defaults/local to get a sense of usage.

You can see a list of dependencies as folders on modules.

Configuration

wes-config.json

Supported properties:

  • All versions:
    • version: number: Configuration version (latest is 2)
    • dependencies: string[]: List of modules to import configurations files from. See modules for all supported dependencies.
  • Version > 2:
    • localOverrides?: string[]: List of file paths from .wes-defaults/local that should be kept as is, not merging with any module's version. Paths shouldn't include a leading /.

License

MIT, https://wes.dev/LICENSE.txt