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

flavor

v0.0.12

Published

Add some flavor

Downloads

3

Readme

npm version

npm downloads

License

Getting Started

Currently, it takes 3* different files to flavor your code, a source file, an output file, and a flavor.config.js file.

$ touch source.js output.js flavor.config.js

In the flavor.config.js file you need to export an array named "keys", and fill it with alias objects:

module.export.keys = [
  {
    alias: /\b(aint)\b/g,
    translation: '!=='
  }
]

When writing your alias specification, make sure to include \b word boundaries to enforce that the keyword must be separate from other characters and omit it when not, like in this regex /\b(unless\()/g.

The above regex would match unless(false) and will translate the unless( part into anything you'd like such as if(!false).

Also note the /g global modifier to ensure this keyword matches in the whole program.

These :key:s will provide flavor with a way to find and replace your aliases with proper code.

Then in your source file write some weird code:

'This string' aint false

Run the flavor command:

$ flavor source.js output.js

And your output.js file should give you real JavaScript.

'This string' !== false

*The output file will be autogenerated by specified path + name if it wasn't created before compile time.

Check out the example for more details

Example Config

Example SourceFile

Use prewritten recipes

Recipe Book

Just download the config file and rename to flavor.config.js or require() it in your config file and concat the array onto your custom flavor.

Note

This is just an experimental project on syntax translation, and is subject to change drastically. Please do not ship this to production.

Please join in on the fun with ideas of your own with a PR or Issue!

forthebadge forthebadge