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

aws-icu

v1.0.1

Published

Getting AWS Lambda to work with ICU during runtime, and working around read-only constraints

Downloads

4

Readme

aws-icu

Handles the short-commings of aws lambdas and NodeJS's requirement for ICU to be loaded at runtime

How it works

You install ICU data in your project,
when you require this module, it synchronously, copies that data to the /tmp directory and Creates AWS_INTL global
which acts similar to the Intl global, but causes a spawn'd process which has ICU to run all your code

Install

node -e 'console.dir("npm install icu4c-data@"+process.config.variables.icu_ver_major+process.config.variables.icu_endianness)'
# install what it tells you

npm i aws-icu --save

Usage

// in your lambda handler js file
require('aws-icu');

//use AWS_INTL instead of INTL or set INTL = AWS_INTL

Example Collator

let collatorEN = new AWS_INTL.Collator('en-us');
let collatorNB = new AWS_INTL.Collator('nb-no');

let en = ['aa', 'a', 'z'].sort( (a, b) => collatorEN.compare(a,b) );
let nb = ['aa', 'a', 'z'].sort( (a, b) => collatorNB.compare(a,b) );

console.log('en_US', en, 'nb_NO',nb);

Outputs

> en_US [ 'a', 'aa', 'z' ] nb_NO [ 'a', 'z', 'aa' ]

Example NumberFormat

let numberEN = new AWS_INTL.NumberFormat('en-us', { style : 'currency', currency : 'USD', currencyDisplay : 'symbol'});
let numberNB = new AWS_INTL.NumberFormat('nb-no', { style : 'currency', currency : 'USD', currencyDisplay : 'symbol'});

console.log('en_US', numberEN.format(7), 'nb_NO', numberNB.format(7));

Outputs

 > en_US $7.00 nb_NO USD 7,00 

Example DateTimeFormat

let dateEN = new AWS_INTL.DateTimeFormat('en-us', {year: 'numeric', month: 'numeric', day: 'numeric'});
let dateNB = new AWS_INTL.DateTimeFormat('nb-no', {year: 'numeric', month: 'numeric', day: 'numeric'});

console.log('en_US', dateEN.format(new Date()), 'nb_NO', dateNB.format(new Date()));

Outputs

> en_US 8/7/2018 nb_NO 7.8.2018