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

@icrules/editor

v0.2.3-alpha.0

Published

> *It sure would be nice if we had an interface to modify the rules and then customize facts to tests out our rules.*

Downloads

4

Readme

@icrules/editor

Reference Rules editor

It sure would be nice if we had an interface to modify the rules and then customize facts to tests out our rules.

I wrote two reference editors, one using plain ol'React and another using the antd UI library. I'll focus on demonstrating the antd based editor library as it brings a better auto-complete among other useful components. You can use the editor code as a reference to either write your own, use it directly in your app or just use it on the examples site to generate your rules.

The editor is data driven by the ICRules Schema and will generate the JSON containing the rules you created along with allowing you to test new facts. Currently the editor is very alpha phase as is and is not fully tested.

import { ICRulesEditorAntd } from '@icrules/editor';

export const RuleEditor = () => {
  const [activeRules, setActiveRules] = useState(rules);
  const onChange = (rules: RuleGroup) => setActiveRules(rules);

  return(
    <ICRulesEditorAntd {...{ facts, rules: activeRules, onChange }} />
  );
}

You can play with the editor right now on the example page (it's very alpha) examples

The antd editor looks like this...

It has the following features:

  • Facts editor
  • Rule Editor

The JSON you see on the right is not part of the editor, but, the example code and displays

  • the basic JSON schema that the editor is generating.
  • the verbose JSON output using the built-in verbose plugin

stay tuned, it's not done yet