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

osg-rules-updater

v0.2.22

Published

CLI tool which allowing to update rules repository

Downloads

21

Readme

Synopsis

prules -s -t -w [--cheats]

source - path to source in a local folder target - URL to target database (includes target env) world-type - name of rules-type document --cheats - allow cheats

Techincal Info

Project structure

CLI context is ./bin/prules

Logic of all context switches and their defaults is implemented at ./lib/params.js

The module logic is ./lib/rules-updater.js

There is a test fixture on ./test/rules_0/

Parameters and Context switches

implemented at ./lib/params.js

3 levels of cascading defaults:

1 - CLI parameter - switches are described with 'optimist'. 2 - prules.config.js - options that are commonly used - save time in providing them every time 3 - defaults - some of the switches have hardcoded defaults

(*) names are not the same. CLI Switches have short names, but they support full names too. prules.config uses shorter names of it's own

The module logic

implemented at ./lib/rules-updater.js

Waterfall with these stages: 1 - getWorldType - gets World Type document from target DB 2 - setVersion - checks version 3 - setParts - update parts on the document 4 - updateWorldType - puts the updated document back to the target DB

important section is the strategy pattern of setPart.

Since in JS functions are first-class objects - the function itself is the dictionary of strategies.

setParts uses a forEachLimit( .., 1 , ...) - for two reasons:

1 - resolving dependency in chdir in async way will make things a little complicated 2 - the output is clearer this way

it is OK to slow down this simple CLI tool...