Registry / devops / fnumber

fnumber

JSON →
library0.1.0jsnpmunverified

A tiny number formatter, v0.1.0. Formats numbers with commas as thousands separators. Minimal and dependency-free. No updates since initial release; stable for simple use cases but lacks customization or advanced formatting options (e.g., decimals, locales). Current version is 0.1.0, with a low release cadence (only initial version).

npm install fnumber
INSTALL
IMPORT
SIG · FNUMBER
F
fnumber
devopsjavascriptv0.1.0
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

default
import formatNumber from 'fnumber'
import { formatNumber } from 'fnumber'
Package is CommonJS, no named export. Default export is function.
require
const formatNumber = require('fnumber')
const fnumber = require('fnumber'); fnumber(...)
CommonJS usage as shown in README.
TypeScript default import
import formatNumber from 'fnumber'
import * as formatNumber from 'fnumber'
No types included; use default import with allowSyntheticDefaultImports or esModuleInterop.

Demonstrates basic usage: formatting numbers with thousands separator.

import formatNumber from 'fnumber'; console.log(formatNumber(999999)); // '999,999' console.log(formatNumber(1234567)); // '1,234,567'
Debug
Known issues
gotchaOnly supports comma separators for thousands; no options for decimals, locales, or custom separators.
fix
Use Intl.NumberFormat for locale-aware formatting or implement custom logic.
affects: >=0.0.0
deprecatedNo updates since initial release; consider using Intl.NumberFormat instead.
fix
Replace with native Intl.NumberFormat or a maintained library like numeral.
affects: >=0.1.0
Errors
Common errors & fixes
TypeError: formatNumber is not a function
Using named import instead of default import in ES6.
fix
Use 'import formatNumber from "fnumber"' instead of 'import { formatNumber } from "fnumber"'.
Cannot find module 'fnumber'
Package not installed or incorrect path in TypeScript without proper module resolution.
fix
Run 'npm install fnumber' and ensure tsconfig.json has 'allowSyntheticDefaultImports' or 'esModuleInterop'.
Upgrade
Version history
0.1.0latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
2 hits · last 30 days
node
2
Resources
fnumber — npm install fnumber · libregistry