hckhanh / read-vn-number Goto Github PK

View Code? Open in Web Editor NEW

7.0 2.0 2.0 90.46 MB

Read Vietnamese number like a Vietnamese

Home Page: https://codesandbox.io/s/0p03j9poq0

License: MIT License

TypeScript 60.53% JavaScript 39.47%

reader read number vn vietnam vietnamese vietnamese-language vietnamese-currency currency vnd

read-vn-number's Introduction

read-vn-number

This is a helper that convert a number to a string like the way a real Vietnamese read it.

Warning

This package is no longer maintained, please migrate to the new package: https://jsr.io/@hckhanh/vn-number/doc/~/readVnNumber

Installation

# npm
npm i read-vn-number

# yarn
yarn add read-vn-number

# pnpm
yarn add read-vn-number

# jsr
npx jsr add @hckhanh/read-vn-number
yarn dlx jsr add @hckhanh/read-vn-number
pnpm dlx jsr add @hckhanh/read-vn-number

GitHub Package Registry (GPR)

https://github.com/hckhanh/read-vn-number/packages

Usage

Import and use in ES6+:

import readNumber from 'read-vn-number'
// import readNumber from '@hckhanh/read-vn-number' // (if you are using jsr)

readNumber('19990000') // or readNumber(19990000)
// output: mười chín triệu chín trăm chín mươi nghìn

or commonjs way:

const readNumber = require('read-vn-number')

readNumber('100000000')
// output: một trăm triệu

License

MIT © Khanh Hoang

read-vn-number's People

Contributors

Stargazers

Watchers

Forkers

trandaison datly

read-vn-number's Issues

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

npm

package.json

@commitlint/cli 18.6.1

@commitlint/config-conventional 18.6.2

@skypack/package-check 0.2.2

@types/node 20.11.20

@typescript-eslint/eslint-plugin 7.0.2

@typescript-eslint/parser 7.0.2

dependency-cruiser 16.2.1

eslint 8.57.0

husky 9.0.11

prettier 3.2.5

semantic-release 23.0.2

ts-node 10.9.2

typescript 5.3.3

vitest 1.3.1

Check this box to trigger a request for Renovate to run again on this repository