|
1 | 1 | # smol-toml |
2 | | -[](https://toml.io/en/v1.0.0) |
| 2 | +[](https://toml.io/en/v1.1.0) |
3 | 3 | [](https://github.com/squirrelchat/smol-toml/blob/mistress/LICENSE) |
4 | 4 | [](https://npm.im/smol-toml) |
5 | 5 | [](https://github.com/squirrelchat/smol-toml/actions/workflows/build.yaml) |
|
8 | 8 | [](https://npm.im/smol-toml) |
9 | 9 | [](https://npm.im/smol-toml) |
10 | 10 |
|
11 | | -A small, fast, and correct TOML parser and serializer. smol-toml is fully(ish) spec-compliant with TOML v1.0.0. |
| 11 | +A small, fast, and correct TOML parser and serializer. smol-toml is fully(ish) spec-compliant with TOML v1.1.0. |
12 | 12 |
|
13 | 13 | Why yet another TOML parser? Well, the ecosystem of TOML parsers in JavaScript is quite underwhelming, most likely due |
14 | 14 | to a lack of interest. With most parsers being outdated, unmaintained, non-compliant, or a combination of these, a new |
@@ -144,8 +144,11 @@ const localTime = TomlDate.wrapAsLocalTime(jsDate) |
144 | 144 |
|
145 | 145 | ## Performance |
146 | 146 | > [!NOTE] |
147 | | -> These benchmarks are starting to get a bit old. They will be updated in the (hopefully near) future to better |
148 | | -> reflect numbers of the latest version of smol-toml on the latest version of Node.js. |
| 147 | +> These benchmarks are starting to get quite old and were ran prior to the release of TOML 1.1.0 which changed subtle |
| 148 | +> implementation details. |
| 149 | +> |
| 150 | +> They will be updated in the (hopefully near) future to better reflect numbers of the latest version of smol-toml |
| 151 | +> on the latest version of Node.js. |
149 | 152 |
|
150 | 153 | A note on these performance numbers: in some highly synthetic tests, other parsers such as `fast-toml` greatly |
151 | 154 | outperform other parsers, mostly due to their lack of compliance with the spec. For example, to parse a string, |
|
0 commit comments