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

cactus-utils

v0.0.3

Published

Cactus Utilities monorepo

Downloads

1

Vulnerabilities

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

Links

Git

Maintainers

cactus-admincactus-admin

Keywords

Readme

cactus-utils

hero

Cactus Utilities monorepo

Table of contents

Packages

| Package | Description | | ---------------------------------------------------------------------: | :------------------------------------------------------ | | @cactus-technologies/node-application | Helper to manage PM2 App definitions and process states | | @cactus-technologies/errors | Errors module for Cactus Servers and Applications | | @cactus-technologies/logger | Customized Pino Logger for Cactus projects | | @cactus-technologies/slack-notifier | Slack Notifications Manager | | @cactus-technologies/api-request | Request helper | | @cactus-technologies/server | Basic Server for Cactus Webservices | | @cactus-technologies/utils | Utility functions for node base apps | | @cactus-technologies/uuid | A set of Unique ID generators for JS apps |

Getting started

First, ensure you have Node v10+ and yarn v1.0+ installed on your machine.

  • Lerna manages inter-package dependencies in this monorepo.
  • Builds are orchestrated via lerna run and NPM scripts.
  • Our documentation is generated from JSDoc comments, README.md, example.js files via CI.

Installation

git clone [email protected]:CactusTechnologies/cactus-utils.git cactus-utils
  cd cactus-utils
  npm install

Incorporating upstream changes

If you were previously in a working state and have just pulled new code from develop:

  • If there were package dependency changes, run yarn at the root.
    • This command is very quick if there are no new things to install.
  • Run yarn compile to get the latest built versions of the library packages in this repo.
    • This command is quicker than yarn verify since it doesn't run tests

Developing packages

Thanks for taking the time to care about the codebase! :tada: :confetti_ball: :+1:

  1. Create a new feature branch. We use a format like [initials]/[feature]: jp/refactor-api.
  2. Write some code. :hammer:
  3. Ensure your code is tested??? and linted.
    • Add unit tests as necessary when fixing bugs or adding features; run them with yarn test in the relevant packages/ directory. (Wishfull thinking for the moment.)
    • Linting is best handled by your editor for real-time feedback.
    • If you use VS Code the project will recommend you to install the appropriate extentions.
    • Most lint errors can often be automatically fixed. Run lint fixes with yarn fix.
  4. Submit a Pull Request.
  5. Team members will review your code and merge it after approvals.
    • You may be asked to make modifications to code style or to fix bugs you may have not noticed.
    • Do not amend commits and push --force as they break the PR history. Please add more commits.
  6. Hooray, you helped! :tophat:

Maintainers

License

MIT © Cactus Technologies LLC