Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NPM does not seem up-to-date #31

Open
kefniark opened this issue Jun 17, 2020 · 3 comments
Open

NPM does not seem up-to-date #31

kefniark opened this issue Jun 17, 2020 · 3 comments

Comments

@kefniark
Copy link

Description

The version on npm seem to be slightly off compared to the latest branch

It's still the 2.2.5 and not the 3.0

@iarna
Copy link
Owner

iarna commented Jul 5, 2020

It's published to npm on a tag, so you can npm install @iarna/toml@toml-1.0.0-rc.1 and get it. Probably it is time to flip that to latest tho.

Edited to add: The reason I was holding off is that the stringifier currently can generate results that are not compatible with previous versions. Previously if you said TOML.stringify({a: [1, 2.3]}) it would produce a = [ 1.0, 2.3 ] but with 3.0.0 and TOML 1.0.0 compat it produces a = [ 1, 2.3 ]. The latter can't be parsed by earlier TOML parsers.

@GrosSacASac
Copy link

iarna thanks for the good work :)

@viceice
Copy link

viceice commented Oct 31, 2022

please tag V3 as latest, toml V1 is also released since some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants