The TOML spec says that numbers can lie in the range of 64-bit signed integers. This presents a problem for JavaScript implementations of TOML, since the entire range of 64-bit signed integers can't be represented exactly by JavaScript. In particular, only the closed range of integers [Number.MIN_SAFE_INTEGER, Number.MAX_SAFE_INTEGER] can be represented exactly by the JavaScript number primitive.

To demonstrate that this is a problem for toml-node, check this out:

> require('toml').parse('max_safe = 9007199254740991\n' +
    'max_safe_plus_two = 9007199254740993')
{ max_safe: 9007199254740991,
  max_safe_plus_two: 9007199254740992 }

There are a few ways to deal with this problem (parse large ints as strings, depend on a BigInteger library for large ints, throw RangeErrors, among others). I don't have a strong opinion on which option is best, but I do think the library should address this issue in some way!