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

nrlint

v1.2.0

Published

Linter for Node-RED flows

Downloads

1,974

Readme

nrlint - Node-RED Flow Linter

nrlint is a linting tool for identifying potential problems with Node-RED flows.

It can be used within the Node-RED editor or run as a command-line tool.

Installation and Usage

In the editor

In your Node-RED user directory (typically ~/.node-red), run:

npm install nrlint

You can then generate a default configuration file with:

npx nrlint --init > .nrlintrc.js

Edit your Node-RED settings file, ~/.node-red/settings.js and add the follow inside the module.exports block. Remember, each entry in the block must be separated by a comma (,).

module.exports {
    // Add a `nrlint` entry pointing to your nrlint config file
    nrlint: require("./.nrlintrc.js"),
}

Finally, restart Node-RED.

In the editor you will now have a linter sidebar available. It will report any warnings or errors the linter detects whilst you edit your flows.

The cog icon at the top of the sidebar allows you to customise your linter configuration. Note that doing so will not modify the .nrlintrc.js file you created - the new configuration will be stored in the editor preferences.

Command-line usage

You can run nrlint as a command line tool to lint a local json flow file.

Following the instructions above to install nrlint. You can then run it from the ~/.node-red directory using npx:

npx nrlint myFlowFile.json

Run with --help to see the available options.

Developing

To use the development version of nrlint you can clone its source code repository and build it yourself.

  1. Get the source code
git clone https://github.com/node-red/nrlint.git
  1. Install the dependencies
cd nrlint
npm install
  1. Build the plugin
npm run build
  1. Install into Node-RED
cd ~/.node-red
npm install <path-to-nrlint-directory>
  1. Restart Node-RED to load the linter.

Source code structure

  • bin - CLI executable
  • lib - main source code of the linter
    • cli - source code of the CLI
      • formatters - source code of the output formatters used by the CLI version
    • rules - source code of the built-in rules
      • function-eslint - source code of the built-in function-eslint rule.
  • scripts - build scripts used by npm run build
  • src - source code of the plugins

After npm run build is run, the following directories will be created:

  • dist - contains the built plugin files
  • resources contains the built Worker files

## Acknowledgements

nrlint is modelled after eslint and borrows many of its concepts.