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

text-to-js-identifier

v0.0.4

Published

Turn arbitrary text to a valid javascript identifier

Downloads

49

Readme

Text to JS Identifier

Turn arbitrary text into a valid javascript identifier.

I found this code useful as I have been experimenting with building languages that compile into javascript in my spare time. Often I prefer to use identifiers that allow more characters that javascript does.

Use

npm

If you are using node.js, install with npm:

$ npm install text-to-js-identifier

then use it in your file like so:

var to_js_identifier = require("text-to-js-identifier");
to_js_identifier("hey!"); // -> "hey_$exclamationmark_"

ender

If you are using ender, then add it to your library:

$ ender add text-to-js-identifier

and use it like this:

$.to_js_identifier("bool?"); // -> "bool_$questionmark_"

other

If you aren't using node or ender, then the function can be found in your global scope after you have downloaded and included your file:

to_js_identifier("pretty easy"); // -> "pretty_$space_easy"

Technical Details

If your text happens to be a javascript keyword, then the keyword will be wrapped in _$ and _ (in fact, all replaced values are wrapped this way):

in            -> _$in_
throw         -> _$throw_
function      -> _$function_

If your text contains an invalid character, it will in most cases be replaced by a human-readable and javascript-compatable representation of that character:

-             -> _$dash_
.             -> _$period_
~             -> _$tilde_

If we don't have a handy human-readable representation on hand, we just display the ASCII character code:

0             -> _$ASCII_48_
†             -> _$ASCII_8224_
ƒ             -> _$ASCII_402_

If the text contains a part that is wrapped in _$ and _ (in other words, if it looks like a generated identifier), we will escape that with another set of wrappings. This is so that it is not possible to have two bits of different text generate the same identifier:

_$hey_        -> _$_$hey__
_$in_         -> _$_$in__
_$ASCII_402_  -> _$_$ASCII_402__

All text that is already valid will simply pass through unchanged:

hey           -> hey
?wassup       -> _$questionmark_wassup
etc.          -> etc_$period_
hey,you       -> hey_$comma_you

As you can see, replacement values can go anywhere. Any ASCII-compatable string should generate a valid javascript identifier.