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

waudbase64

v1.0.7

Published

Base64 generator for waud.js

Downloads

16

Readme

waudbase64 npm version

Base64 generator for waud.js

Base64 decoding is widely supported across all browsers.

###Installation

npm install -g waudbase64

###Usage

waudbase64 -i sounds -o sounds.json

###Help

waudbase64 --help
info: Usage: waudbase64 -i sounds -o sounds.json
info: Options:
  --input, -i         input folder (default: ./)                
  --output, -o        output JSON file (default: sounds.json)   
  --noBasePath, --nb  doesn't prepend base path to each asset id
  --help, -h          help

###Example with waud.js

var base64pack = new WaudBase64Pack("assets/sounds.json", _onLoad);

function _onLoad(snds:Map<String, IWaudSound>) {
  snds.get("assets/beep.mp3").play();
}

###Sample

http://waud.github.io/sample/base64.html

###More Info

Note that the file size of base64 encoded JSON file will be more than the actual sound file(s).

But if your web server have gzip compression enabled for JSON files then the network transfer size will be smaller than loading individual sound files.

Enabling gzip compression is a standard practice and most likely your web server has it enabled already and to verify that you can open the network tab in chrome developer tools and click on any JSON file that's loaded. If you notice Content-Encoding:gzip in Response Headers section then it's already enabled.

Some numbers for example:

Size of 6 individual mp3 sound files before base64 encoding: 589 KB

Size of base64 encoded JSON with all the 6 sounds: 785 KB

Network transfer size with gzip enabled: 552 KB

Licensing Information

This content is released under the MIT License.

Contributor Code of Conduct

Code of Conduct is adapted from Contributor Covenant, version 1.4