Publish v1 on npm

[KoryNunn]

Can this module be published as version 1 on npm so that it can be updated via npm up

[medikoo]

Version v1 will be published at some point, but If I read correctly0.x versions also should work with npm up as expected (?)

[KoryNunn]

It has issues: npm/node-semver#79

[medikoo]

@KoryNunn the issue you mention, probably refers only to 0.0.x versions, while es6-map is at 0.x.x currently, and that should work without issues. See npm/node-semver#41 (comment)

[KoryNunn]

If that is how it works, it's still probably a good idea to put it to 1 as soon as possible, assuming reasonable stability and completion, otherwise people who are using your module will no longer get the latest version at an arbitrary point because you updated to 1.

This exact issue happened to me with your weak-map module, which I installed before v1 was released. I nearly submitted a duplicate of #2 because I didn't get v1 through npm up

[medikoo]

It's very good that npm up won't switch from 0.x to 1.0, otherwise it'll be a critical bug in npm up.

At this point I don't see any issue, switch between 0.1 and 1.0 should be considered as breaking and no tool should do it automatically. That's expected behavior, and npm up works perfectly for current es6-map versions e.g. if I release non breaking 0.1.2 update, npm up will update it for you.

[quantuminformation]

Is there a minified version I can just copy paste, I don't want to use a build system