The 0.1.1 version on npm is not the same as v0.1.1 on GitHub

[kensnyder]

I installed via npm and see that the source code is different from the current master which shows a value of 0.1.1 in the package.json file.

I prefer the GitHub version because it ignores undefined values instead of the npm version which throws exceptions:

            undefined: function (x) {
                throw new Error("rison can't encode the undefined value");
            }

I don't know if the npm version is older or newer. I don't know if the behavior of ignoring undefined values is what you want moving forward. So for now, I'm going to put the GitHub repo and commit version in my own package.json.

It would be great to have the two sync'ed, and, if possible, keep the behavior of ignoring undefined values. It is not a simple task to recursively remove all the undefined values by hand. Ignoring in the parser makes the most sense.

[Nanonid]

npm owner ls rison
jonasfj jopsen@gmail.com

Is sitting on rison.
I could publish as risonjs etc. or just checkout from github.
Ideas?

[kensnyder]

Ah. I didn't realize this was a fork of rison. Thanks for your work! Well there are a few things to do for sure:

• In README.md, specify that this is a fork of the npm version of rison, why the fork was created, and how it is different. I know you added "Rison mirror of now dead site" but I didn't and don't know what that means exactly.
• Use a different version number than the npm rison. Maybe bump to v1.0.0 or v2.0.0 and use semver.

I do like the idea of putting this rison on npm (risonjs or rison-js sound nice) but I can live without that. It's up to you if you want to put in the time.

[brody2consult]

Hi @Nanonid according to https://docs.npmjs.com/misc/disputes and similar documents: you should be able to get the right to publish updates to the npm rison package if you follow the procedure described there.

I think you have an especially strong case because the other guy published from a fork 2 years ago and did not keep up with your changes.

I would personally favor bumping to a 0.2.0 version number or something to make it very clear that there is something new.

I sincerely hope you will pursue this and wish you the best of luck here. I read that they will probably want to wait at least 4 weeks if you don't get a response from the other guy. Thanks for your efforts!

[bryanrideshark]

I would like to get behind rison development as well, it would be much easier if an official npm package existed.