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

cesu-8

v0.0.1

Published

Convert a UTF-8 buffer to a CESU-8 string

Downloads

6

Readme

#CESU-8 Encoding for Node.js

###An Explanation

At the moment, Node is punting on non-BMP unicode characters. What to do?

An unsatisfactory workaround was to manually do the unwinding, as proposed here: http://code.google.com/p/v8/issues/detail?id=761#c8

Which does in fact work, see: https://gist.github.com/1696314

Though it seems rather brittle. What happens if String.fromCharCode returns a { and garbles the JSON? Clearly not the answer.

So what's the problem? Why doesn't it work to begin with? Well, v8 doesn't support strict UTF-8, meaning that handing it a UTF-8 encoded buffer is never going to work, unless Javascript itself changes. (N.B. There is a strawman proposal)

But clearly something can be done 'cause the browser is working around the problem. From what I've surmised, using CESU-2 encoding, in lieu of UTF-8, will work. At least, that's what the browser appears to be doing.

To do the encoding, I looked at: http://www.unicode.org/reports/tr26/

This library shows that you can take a UTF-8 encoded buffer, convert it to UTF-16 with node-iconv and then build a string with the surrogate pairs. There are a few issues with this, String.length will be one longer than expected, but that's the way it should work and does in the browser. But otherwise parsing JSON, the original use case, will be fine.

This can probably be done purely in Javascript, ie. no libiconv, or even pushed down to C++, as a new encoding, CESU-8.

###Install

With everyone's favourite package manager,

npm install cesu-8

###Example Usage

var cesu = require('cesu-8')

// emoji � � �
var arr = [
  101, 109, 111, 106, 105, 32, 240, 159, 141, 168,
  32, 240, 159, 141, 169, 32, 240, 159, 141, 170
]  // these are the octets for the above string in utf8

var utf8buffer = new Buffer(arr)

var mystring = cesu.toString(utf8buffer)

// do whatever you want with the string
// have fun
// seriously

// convert it back to a buffer
var backtobuf = cesu.toBuffer(mystring)
process.stdout.write(backtobuf)

###Todo

  • Find out what the first char is: 0xFFEF
  • Remove iconv dependency.