Comparing version 0.5.0 to 0.5.1
{ | ||
"name": "fast-toml", | ||
"version": "0.5.0", | ||
"version": "0.5.1", | ||
"description": "Fast and light parser for TOML 0.5, an alternative to JSON or YAML file formats.", | ||
@@ -5,0 +5,0 @@ "main": "fast-toml.js", |
@@ -97,5 +97,6 @@ # Fast TOML Parser for Node.js | ||
| Hot round | **0.501** | 0.604 | 0.627 | 6.639 | | ||
| Package size (including dependencies, readme, sourcemaps, ...) | **13.8 ko** | 93.1 ko | 261 ko | +3000 ko | | ||
| Package size | **13.8 ko** | 93.1 ko | 261 ko | +3000 ko | | ||
The comparison has been made in a Node 11.2.0 environment with this medium-size [sample TOML file](https://gist.github.com/robmuh/7966da29024c075349a963840e2298b2), which covers about all the different ways to use TOML. | ||
@@ -119,3 +120,3 @@ | ||
- the source code (+ your tests + dev dependencies), should be on github/gitlab or similar. Users who want to collaborate on your project will `git clone` it (not `npm install` it). | ||
- the source code (+ your tests + dev dependencies), should be on github/gitlab or similar. Users who want to collaborate on your project will **git clone** it (not **npm install** it). | ||
- your npm package should only contain the *useful code* (production-ready). When you use a third party library, you expect it has been battle-tested and you don't need the development version. If you have several versions of your code (CommonJS, ESmodules, browser), you should have one package for each of these versions. | ||
@@ -122,0 +123,0 @@ |
131
13795