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

@cgignite/ignite-jsonata

v1.0.3

Published

JSONata node for Ignite

Downloads

3

Vulnerabilities

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

Links

Git

Maintainers

slabrador09slabrador09

Keywords

node-red

Readme

@cgignite/ignite-jsonata

Node-RED node for JSONata Dynamically set the JSONata query and run over a JSON string returning the result within the message.

Message Inputs

  • msg.payload (default) = JSON string to be queried. This can be change within the node options
  • msg.jsonata = JSONata query to be used.

Message Outputs

  • msg.jsonataResult (String) = The result returned. Only returned if the JSONata query is successful otherwise will be undefined.
  • msg.jsonataStatus (String) = The status message, success or errored returned.
  • msg.jsonataByMsg (Boolean) = The message (msg.jsonata) JSONata query was used, returning true. False, if the node options (JSONata Query) was utlised. Only defined when a result (msg.jsonataResult) is returned.

Message Status

The status returned either on the message (msg.jsonataStatus) or displayed below the node when executed.

  • Success, Successful query and the msg.jsonataResult with have the result.
  • No JSONata result, The JSONata query provided no result when queried.
  • No JSONata provided, The JSONata query is missing from the message (msg.jsonata) or not set in the node options (JSONata Query).
  • Invalid JSON string, JSON string provided is invalid or malformed.
  • No JSON string provided, JSON string is missing from the message (msg.payload, default).

Note

When JSONata is set within the message (msg.jsonata) and the node options (JSONata Query) the message (msg.jsonata) has priority, the JSONata query in the node options will be ignored. Allowing a static JSONata query to be set and dynamically changed as required.

Author

Ignite Platform Team