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

utf8safe-js-stringify

v0.1.4

Published

Generate JS(ON) code that re-creates a JS value (object, string, Date, …) as verbatim as possible on the other side of a UTF-8 stream.

Downloads

12

Readme

utf8safe-js-stringify

Generate JS(ON) code that re-creates a JS value (object, string, Date, …) as verbatim as possible on the other side of a UTF-8 stream.

The problem: silent data loss

Some UCS-2 characters cannot be encoded as UTF-8. When you try to send them over a stream with UTF-8 encoding, they will usually be replaced with U+FFFD without warning. After conversion they all look the same, so this loss of data is irreversible.

A perfect trap setup for sneaky bugs: As long as all your data is UTF-8, you won't notice this problem. When you do, maybe because some .substr() has split a surrogate pair, you'll probably dump the "buggy" data over yet another UTF-8 stream, see U+FFFD, and think it's really about the data. (Assuming you forgot above lecture by then.) After all, your browser (or file or whatever) received exactly the same bytes that were in your debug dump, so you go examine your data sources…

Are your programs at risk?

Popular UTF-8 streams include nodejs's stdin, stdout, stderr and thus console in default config. Also its fs, net, http and https modules by default use UTF-8 for their streams.

Usage

Same as js-stringify.

This module really just escapes UTF-8-incompatible characters (and verbatim U+FFFD) from js-stringify's output:

module.exports = require('utf8safe-uhex').conv(require('js-stringify'));

License

ISC