Packages

@iarna/toml

2.2.5 · 22 Apr 2020ISC12M / weekRepositoryHomepagenpmAtom feed

Upgrading @iarna/toml from 1.7.1 to 2.0.0

1 release in betweenevery note read

Other targets from 1.7.1Latest2.2.5
The note of 2.0.0 lists no breaking change or deprecation, which is rare for a major.
?
changes to make
0
advisories fixed
0
new
0
fixes
12 other lines we could not sort, mostly version bumps
  • Delete characters (U+007F) are not allowed in plain strings. You can include them with escaped unicode characters, eg \u007f.

    2.0.0
  • Integers are specified as being 64bit unsigned values. These are supported using BigInts if you are using Node 10 or later.

    2.0.0
  • Keys may be literal strings, that is, you can use single quoted strings to quote key names, so the following is now valid: 'a"b"c' = 123

    2.0.0
  • The floating point values nan, inf and -inf are supported. The stringifier will no longer strip NaN, Infinity and -Infinity, instead serializing them as these new values..

    2.0.0
  • Datetimes can separate the date and time with a space instead of a T, so 2017-12-01T00:00:00Z can be written as 2017-12-01 00:00:00Z.

    2.0.0
  • Datetimes can be floating, that is, they can be represented without a timezone. These are represented in javascript as Date objects whose isFloating property is true and whose toISOString method will return a representation without a timezone.

    2.0.0
  • Dates without times are now supported. Dates do not have timezones. Dates are represented in javascript as a Date object whose isDate property is true and whose toISOString method returns just the date.

    2.0.0
  • Times without dates are now supported. Times do not have timezones. Times are represented in javascript as a Date object whose isTime property is true and whose toISOString method returns just the time.

    2.0.0
  • Keys can now include dots to directly address deeper structures, so a.b = 23 is the equivalent of a = {b = 23} or [a] b = 23. These can be used both as keys to regular tables and inline tables.

    2.0.0
  • Integers can now be specified in binary, octal and hexadecimal by prefixing the number with 0b, 0o and 0x respectively. It is now illegal to left pad a decimal value with zeros.

    2.0.0