Packages

@iarna/toml

2.2.5 · 22 Apr 2020ISC12M / weekRepositoryHomepagenpmAtom feed

Upgrading @iarna/toml from 1.7.1 to 2.2.5

9 releases in betweennotes for 8

The note of 2.0.0 lists no breaking change or deprecation, which is rare for a major.
?
changes to make
0
advisories fixed
4+
new
11+
fixes

Counted from 8 of 9 release notes. Advisories are counted from the advisory database, in full.

Release by release

  1. 2.2.5no release note

  2. 2.2.4

    21 Apr 20201 new
    • new

      Added Node 12 and 13 to Travis. (Node 6 is failing there now, mysteriously. It works on my machine™, shipping anyway. 🙃)

  3. 2.2.3nothing new or fixed in the note

  4. 2.2.2

    18 Feb 20191 new · 1 fix
    • new

      @ltd/j-toml

    • fixed

      Support parsing and stringifying objects with __proto__ properties. (@LongTengDao)

  5. 2.2.1

    28 Nov 20182 fixes
    • fixed

      Fix bug where keys with names matching javascript Object methods would error. Thanks @LongTengDao for finding this!

    • fixed

      Fix bug where a bundled version would fail if util.inspect wasn't provided. This was supposed to be guarded against, but there was a bug in the guard. Thanks @agriffis for finding and fixing this!

  6. 2.2.0

    13 Sep 20181 new · 2 fixes
    • new

      Typescript: Lots of improvements to our type definitions, many many to @jorgegonzalez and @momocow for working through these.

    • fixed

      Very large integers (>52bit) are stored as BigInts on runtimes that support them. BigInts are 128bits, but the TOML spec limits its integers to 64bits. We now limit our integers to 64bits as well.

    • fixed

      Fix a bug in stringify where control characters were being emitted as unicode chars and not escape sequences.

  7. 2.1.1

    3 Sep 20181 fix
    • fixed

      Oops, type defs didn't end up in the tarball, ty @jorgegonzalez‼

  8. 2.1.0

    1 Sep 20181 new · 5 fixes
    • new

      Types for typescript support, thank you @momocow!

    • fixed

      stringify: Always strip invalid dates. This fixes a bug where an invalid date in an inline array would not be removed and would instead result in an error.

    • fixed

      stringify: If an invalid type is found make sure it's thrown as an error object. Previously the type name was, unhelpfully, being thrown.

    • fixed

      stringify: Multiline strings ending in a quote would generate invalid TOML.

    • fixed

      parse: Error if a signed integer has a leading zero, eg, -01 or +01.

    • fixed

      parse: Error if _ appears at the end of the integer part of a float, eg 1_.0. _ is only valid between digits.

19 other lines we could not sort, mostly version bumps

  • Bug fix: Plain date literals (not datetime) immediately followed by another statement (no whitespace or blank line) would crash. Fixes #19 and #23, thank you @arnau and @jschaf for reporting this!

    2.2.4

  • Bug fix: Hex literals with lowercase Es would throw errors. (Thank you @DaeCatt for this fix!) Fixed #20

    2.2.4

  • Some minor doc tweaks

    2.2.4

  • @sgarciac/bombadil -> 2.1.0

    2.2.2

  • Toml -> 3.0.0

    2.2.2

  • BurntSushi's comprehensive TOML 0.4.0 test suite is now used in addition to our existing test suite.

    2.1.0

  • You can see exactly how the other JS TOML libraries stack up in testing against both BurntSushi's tests and my own in the new TOML-SPEC-SUPPORT doc.

    2.1.0

  • 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

3 internal lines (docs, tests, tooling) left out.