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

nsed

v4.0.5

Published

Javascript Terminal String Editor

Downloads

186

Readme

nsed

Version Dependencies Build Coverage

https://sw.cowtech.it/nsed

Javascript Terminal String Editor: NSed brings Node.js power to the command line.

It works similarly to the standard GNU sed command, with the exception that everything is Javascript and powered by Node.js.

For instance, the following command computes the hash of each file in the test folder:

find test -type f | nsed -r fs -r crypto -c 'fs.readFileSync($data, "utf8")' -c 'crypto.createHash("md5").update($data).digest("hex")'

Installation

To install, simply use npm or yarn:

npm install -g nsed

Overview

Basic usage

Each command is executed on the output of the previous one. You can reference $data for the current input and $index for the current position in the input.

If operating directly on properties or methods of the input, you can omit $data.

find test -type f | nsed -r fs -c 'fs.readFileSync($data, "utf8")' -c '.length'

To see all the available options, use -h|--help option.

Filters

Input lines can be filtered out by using filter (-f|--filter) or reverse filters (-F|--reverse-filter) that, respectively, will include the input if the result of the evaluation is a truthy or falsy value (according to Javascript rules).

For instance, the following command will print only files starting with index:

find test -type f | nsed -f '/^index/'

Regular expressions

Regular expression can be used in commands and referenced later, using $NUMBER syntax.

For instance, the following command will print the second letter of each file:

find test -type f | nsed -c '.replace("test/", "")' -c '/.(.).+/' -c '$1'

Advanced usage

Before processing commands, you can instruct nsed to require any available Node.js modules, by using -r|--require switch. The module will be available with its name camelcased. For instance, -r string_decoder will make stringDecoder available for your commands.

Finally, instead of providing commands via command line, you can input Javascript file using -s|--source switch. The source file must export a function which accepts a string ($data representing the current line) and a number ($index, representing the current line in the input).

ESM Only

This package only supports to be directly imported in a ESM context.

For informations on how to use it in a CommonJS context, please check this page.

Contributing to nsed

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
  • Fork the project.
  • Start a feature/bugfix branch.
  • Commit and push until you are happy with your contribution.
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.

Copyright

Copyright (C) 2017 and above Shogun [email protected].

Licensed under the MIT license, which can be found at https://choosealicense.com/licenses/isc.