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

sed

v0.0.2

Published

Embrace and extend GNU sed, the stream editor for filtering and transforming text.

Downloads

1,762

Readme

sed

Embrace and extend GNU sed, the stream editor for filtering and transforming text.

 



Stability: Alpha preview

  • Some parts seem to somewhat work already.
  • The transform part is currently hard-coded to the equivalent of sed -re 's~^~>> ~;s~$~ <<~;$a done.'
  • Uploading to npm anyway in order to announce the new repository.


 

CLI

See docs/cli/.

API

This module ESM-exports an object with these methods:

.cliMain(args)

Interpret the CLI arguments given in array args. Returns a promise for completion.

  • While I try to keep the script syntax mostly compatible with GNU sed, the CLI arguments are very different. If you need a tool with same CLI arguments as the original GNU sed, please use GNU sed.

.transform(state[, input])

Transform text according to state, which should be an object with a property parseTree, whose value should be the result of .parse-ing a sed script.

If input is…

  • null or undefined (e.g. not given), return a transform stream that you can pipe your text into.
  • a string, return a promise for the transformed stream.
  • a buffer, it will be converted to a string using node's default encoding, then processed as if that string was given.

In addition to the mandatory parseTree property, state may contain any of these optional properties:

  • prFs: An object with an interface similar to the Node.js fs Promises API. Providing it will enable script commands that need file system access.

.parse(script[, grow])

Parse sed commands from string script. Returns a promise for an opaque truthy value that represents the resulting parse tree. The only purpose of exposing the parse tree is so that you can reuse it for multiple invocations of .transform, so avoid relying on its internal structure in any way.

If grow is provided, it is expected to be an existing parse tree, and that one will be extended in-place rather than creating a new one.

Known issues

  • Needs more/better tests and docs.

 

License

ISC