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

@vlab-research/translate-typeform

v0.2.6

Published

Translates Typeform forms to Facebook Messenger format.

Readme

translate-typeform

Translates Typeform forms to Facebook Messenger format.

Number Fields with Locale

To support international number formats in number fields, add locale to the field description in YAML:

locale: de-DE

Supported locales:

  • en-US (default) - US format: 1,234.56
  • de-DE - European format: 1.234,56
  • ar-SA - Arabic Saudi: ١٬٢٣٤٫٥٦
  • ar-MA - Arabic Morocco: 1 234,56

Example Typeform Field Description

For a number field expecting European format input:

locale: de-DE

The validator will then accept 1.234,56 as valid input and correctly parse it as 1234.56.

Number Parsing API

The parseNumber(str, locale) function parses numeric strings with locale-aware formatting.

Usage

const { parseNumber } = require('@vlab-research/translate-typeform')

parseNumber('1,234.56')           // 1234.56 (US format, default)
parseNumber('1.234,56', 'de-DE')  // 1234.56 (European format)
parseNumber('١٢٣', 'ar-SA')       // 123 (Arabic-Indic numerals)

Supported Formats

| Locale | Thousands | Decimal | Example | |--------|-----------|---------|---------| | en-US (default) | , | . | 1,234.56 | | de-DE | . | , | 1.234,56 | | ar-SA | ٬ | ٫ | ١٬٢٣٤٫٥٦ | | ar-MA | (space) | , | 1 234,56 |

Unicode Numeral Support

Automatically normalizes digits from 30+ numeral systems:

  • Arabic-Indic: ١٢٣ -> 123
  • Devanagari: १२३ -> 123
  • Persian: ۱۲۳ -> 123
  • Bengali, Tamil, Thai, and many more

Cross-Locale Behavior

Important: The locale determines how separators are interpreted. Mismatched locale and input format will produce incorrect results.

Works: ar-SA locale with US-style ASCII input

parseNumber('100.50', 'ar-SA')    // 100.5 (correct)
parseNumber('1,234.56', 'ar-SA')  // 1234.56 (correct)

This works because ar-SA separators (٬ thousands, ٫ decimal) normalize to the same ASCII characters as US format (, and .).

Works: Default locale with Arabic script input

parseNumber('١٠٠.٥٠')        // 100.5 (correct)
parseNumber('١٬٢٣٤٫٥٦')      // 1234.56 (correct)

This works because Arabic digits and separators normalize to US-style ASCII.

Broken: ar-MA locale with US-style input

parseNumber('100.50', 'ar-MA')    // 10050 (wrong!)
parseNumber('1,234.56', 'ar-MA')  // 1.23456 (wrong!)

ar-MA uses European-style formatting (comma=decimal, space=thousands). When given US-style input (dot=decimal, comma=thousands), the parser misinterprets the separators.

Rule: Always ensure the input format matches the specified locale.

Returns

  • number - The parsed numeric value
  • null - If parsing fails (invalid input, letters, etc.)