# stringnumber

> JSON.parse and JSON.stringify with a conversion of big numbers into strings

Latest version **0.0.3** (published 2015-11-03) · MIT license · 0 weekly downloads

## Install

```sh
npm install stringnumber
pnpm add stringnumber
yarn add stringnumber
bun add stringnumber
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.0.3 |
| Published | 2015-11-03 |
| First published | 2015-10-30 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 0 |
| Author | Marc Höffl |
| Maintainers | m0c |
| Keywords | JSON, bigint, bignumber, parse, json |

## Links

- npm: https://www.npmjs.com/package/stringnumber
- Repository: https://github.com/KeKs0r/StringNumber
- Homepage: https://github.com/KeKs0r/StringNumber#readme
- Issues: https://github.com/KeKs0r/StringNumber/issues
- npm.io page: https://npm.io/package/stringnumber

## Alternatives

- [@mapbox/jsonlint-lines-primitives](https://npm.io/package/@mapbox/jsonlint-lines-primitives.md) — 5.3M weekly downloads
- [reftools](https://npm.io/package/reftools.md) — 3.5M weekly downloads
- [@hey-api/openapi-ts](https://npm.io/package/@hey-api/openapi-ts.md) — 3.5M weekly downloads
- [@mapbox/geojson-rewind](https://npm.io/package/@mapbox/geojson-rewind.md) — 2.4M weekly downloads
- [turbo-stream](https://npm.io/package/turbo-stream.md) — 1.7M weekly downloads

## Recent versions

- 0.0.3 (latest) — 2015-11-03
- 0.0.2 — 2015-10-30
- 0.0.1 — 2015-10-30

## README

StringNumber
===========

JSON.parse/stringify that converts big numbers into strings. Based on [json-bigint](https://www.npmjs.com/package/json-bigint).

While most JSON parsers assume numeric values have same precision restrictions as IEEE 754 double, JSON specification _does not_ say anything about number precision. Any floating point number in decimal (optionally scientific) notation is valid JSON value. It's a good idea to serialize values which might fall out of IEEE 754 integer precision as strings in your JSON api, but `{ "value" : 9223372036854775807}`, for example, is still a valid RFC4627 JSON string, and in most JS runtimes the result of `JSON.parse` is this object: `{ value: 9223372036854776000 }`

---
_Source: https://npm.io/package/stringnumber · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._