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

normalize-transforms

v2.0.0

Published

Normalize's default transforms via deps-walk

Downloads

9

Readme

Walker Transforms

NPM version Build status Test coverage Dependency Status License Downloads Gittip

For documentation, go to https://normalize.github.io/api.html#transforms.

Adding Transforms

Feel free to add transforms as long as they transform would be used by a lot of people. In other words, please don't add transform for your brand new templating system.

Transforms here are a little odd due to the weird upstream/downstream nature of the middleware as well as the additional responsibilities transforms have, specifically handling dependencies. If you don't know what you're doing, add a lot of tests and debug() statements!

Please lazy-load all external modules unless they're very small. This will help with faster initial load times as well as not throw if the end user doesn't have it installed. Also, your underlying transform library should not be included in dependencies and instead devDependencies.

Creating Custom Transforms

You might want to add your own transforms. Feel free to fork this and use it as a replacement for nlz(1) or your app. You may either fork and use your fork as a git dependency in your app:

{
  "devDependencies": {
    "nlz": "1",
    "normalize-transforms": "jonathanong/transforms.js"
  }
}

Or you may publish it as a separate package and reference it in your .nlzrc:

{
  "devDependencies": {
    "nlz": "1",
    "my-custom-transforms": "1"
  }
}

.nlzrc:

{
  "transform": "my-custom-transforms"
}

When creating your own custom transform as your own package, you don't have to fork this repository. Instead, you can use this repository as a dependency and bundle all the exported transforms like the exported transform() function: https://github.com/normalize/transforms.js/blob/master/lib/index.js

Caveat: if your transform function is a local file, prefix it with ./ so that nlz knows that it's a local file. It will be resolved against process.cwd().