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

subschema-plugin-conditional

v4.1.3

Published

Sometimes you need some dynanicness in your schema. To do this we have conditional. The basic is it listens to a valueManager and then tries show or hide.

Downloads

15

Readme

Sometimes you need some dynanicness in your schema. To do this we have conditional. The basic is it listens to a valueManager and then tries show or hide.

Props:

  • value (optional - any - null) - The value to listen to can if not given, than it will be a compare against not null.

  • listen (optional - string - path) The path to listen to can be empty, in which case will look for defaults to the current path. Can be relative '..' or absolute. Defaults to the current path.

  • template (optional - string|ReactFactory) The template to use if it evaluates to true IE - Modal, ShowHide

  • falseTemplate (optional - string|ReactFactory) The template to use if the expression evaluates to false.

  • animate (optional - boolean|string|object) A string to use a named animation,or a boolean. if a string that string will be the "name" to use to animate. If an object is passed than it will passed as props to the transition group. If === true than the default animation will be used. If === false than no animation is used

  • operator (optional - string|regex - truthy How to compare the value to the matched value. If ommitted and a value is given than === is used. If ommitted and the value is ommitted than a truthy (!!value) is used. The built in operators are: * '==' - Same as javascript == * '>=' * '<=' * '>' * '<' * '===' * '!==' - Special ones - * 'truthy' !!value * 'falsey' !value * '/regex/[gim]' /regex/.test() * '!/regex/[gim]' !/regext/.test(); * 'something registed with the loader'

  • error (optional - string) - The error path to listen to. This path is evaluated slighty differntly, always absolute.

  • dismiss (optional - string) - This will be set to false, given to make the current conditional false. Set this for dismissing modals. If not provided, the template will recieve a dismiss property with the current key substituting '.' with '_' and prepended with an @

See the example