Packages

@iarna/toml

2.2.5 · 22 Apr 2020ISC12M / weekRepositoryHomepagenpmAtom feed

Upgrading @iarna/toml from 1.5.5 to 1.7.1

4 releases in betweenevery note read

Other targets from 1.5.5Latest2.2.5
0
changes to make
0
advisories fixed
1
new
2
fixes

Release by release

  1. 1.7.0 – 1.7.12 releases, nothing new or fixed in the notes

  2. 1.6.0

    28 Jun 20181 new · 2 fixes
    • new

      TOML.stringify: Allow toJSON properties that aren't functions, to align with JSON.stringify's behavior.

    • fixed

      TOML.stringify: Don't use ever render keys as literal strings.

    • fixed

      TOML.stringify: Don't try to escape control characters in literal strings.

  3. 1.5.6nothing new or fixed in the note

13 other lines we could not sort, mostly version bumps

  • Date parsing was rewritten to not use regexps, resulting in a huge speed increase.

    1.7.0

  • Strings of all kinds and bare keywords now use tight loops to collect characters when this will help.

    1.7.0

  • Regexps in general were mostly removed. This didn't result in a speed change, but it did allow refactoring the parser to be a lot easier to follow.

    1.7.0

  • The internal state tracking now uses a class and is constructed with a fixed set of properties, allowing v8's optimizer to be more effective.

    1.7.0

  • Errors in the syntax of your TOML will now have the fromTOML property set to true. This is in addition to the line, col and pos properties they already have.

    1.7.0

  • New Export: TOML.stringify.value, for encoding a stand alone inline value as TOML would. This produces a TOML fragment, not a complete valid document.

    1.6.0

  • String literals are NOT supported as key names.

    1.5.6

  • Accessing a shallower table after accessing it more deeply is ok and no longer crashes, eg:

    1.5.6

  • Unicode characters in the reserved range now crash.

    1.5.6

  • Empty bare keys, eg [.abc] or `` now crash.

    1.5.6