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 🙏

© 2025 – Pkg Stats / Ryan Hefner

unicode-encode

v1.5.1

Published

Easy base64 encode and decode of Unicode strings and Emojis.

Readme

Unicode Encode 👋

npm badge CI Status TypeScript

In most browsers, calling btoa() on a Unicode string or Emojis will cause an InvalidCharacterError or DOMException exception.

This small package provides a simple solution by making available utoa and atou, Unicode to and from base64 encoding.

Install

npm i --save unicode-encode

Usage

JavaScript

// Import the needed functions.
const { utoa, atou } = require("unicode-encode");

// Examples:
utoa("à bientôt ☮"); // w6AgYmllbnTDdHQg4piu
atou("w6AgYmllbnTDdHQg4piu"); // "à bientôt ☮"

utoa("👋 Unicode!"); // 8J+RiyBVbmljb2RlIQ==
atou("8J+RiyBVbmljb2RlIQ=="); // "👋 Unicode!"

TypeScript

// Import with full type support
import { utoa, atou } from "unicode-encode";

// Functions are fully typed
const encoded: string = utoa("Hello 🌍");
const decoded: string = atou(encoded);

API

utoa(str: string): string

Encodes a Unicode string to base64.

  • str: The Unicode string to encode
  • Returns: Base64 encoded string

atou(base64: string): string

Decodes a base64 encoded string back to Unicode.

  • base64: The base64 string to decode
  • Returns: Decoded Unicode string

Development

This project is written in TypeScript and requires Node.js 18+ for development.

Setup

# Clone the repository
git clone https://github.com/Accelery/unicode-encode.git
cd unicode-encode

# Install dependencies
npm install

# Build the project
npm run build

# Run tests
npm test

Available Scripts

  • npm run build - Compile TypeScript to JavaScript
  • npm run clean - Remove compiled output
  • npm run rebuild - Clean and build
  • npm test - Run tests on compiled code
  • npm run test:ts - Run tests directly on TypeScript files
  • npm run test:watch - Run tests in watch mode
  • npm run coverage - Generate test coverage report
  • npm run lint - Check code formatting
  • npm run lint:fix - Fix code formatting
  • npm run typecheck - Check TypeScript types without emitting

Publishing

This package uses automated publishing via GitHub Actions. To publish a new version:

  1. Update the version in package.json
  2. Update the CHANGELOG.md with your changes
  3. Create a new GitHub release with a tag matching the version
  4. The package will be automatically published to NPM

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests for new functionality
  5. Ensure all tests pass and code is properly formatted
  6. Submit a pull request

License

MIT