@iarna/toml
2.2.5 · 22 Apr 2020ISC12M / weekRepositoryHomepagenpmAtom feed
Upgrading @iarna/toml from 1.2.0 to 1.7.1
15 releases in betweenevery note read
Release by release
1.7.0 – 1.7.12 releases, nothing new or fixed in the notes
- 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.
- new
1.5.3 – 1.5.64 releases, nothing new or fixed in the notes
- fixed
parse: Fix a parser bug that would result in errors when trying to parse arrays of numbers or dates that were not separated by a space from the closing ].
- fixed
parse: Fix a bug in the error pretty printer that resulted in errors on the first line not getting the pretty print treatment.
- fixed
stringify: Fix long standing bug where an array of Numbers, some of which required decimals, would be emitted in a way that parsers would treat as mixed Integer and Float values. Now if any Numbers in an array must be represented with a decimal then all will be emitted such that parsers will understand them to be Float.
- fixed
1.3.0 – 1.5.17 releases, nothing new or fixed in the notes
25 other lines we could not sort, mostly version bumps
- 1.7.0
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
fromTOMLproperty set to true. This is in addition to theline,colandposproperties they already have. - 1.6.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.5.6
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 internal line (docs, tests, tooling) left out.