Skip to content
This repository has been archived by the owner on Jun 29, 2018. It is now read-only.

Determine how Babili should be versioned #65

Open
Daniel15 opened this issue Nov 7, 2016 · 3 comments
Open

Determine how Babili should be versioned #65

Daniel15 opened this issue Nov 7, 2016 · 3 comments

Comments

@Daniel15
Copy link
Member

Daniel15 commented Nov 7, 2016

See babel/minify#139

Currently each plugin has its own version number, which makes it difficult to version babili-standalone as a whole.

cc @hzoo

@hzoo
Copy link
Member

hzoo commented Nov 7, 2016

Right now the preset/cli will update with every update in lock-step so it should be ok to version based on the preset only?

@Daniel15
Copy link
Member Author

Daniel15 commented Nov 7, 2016

@hzoo Ahh I see, so I should be fine just using the version number of the preset? Is there any case where a plugin would have its version number updated but the preset wouldn't be updated?

@Daniel15
Copy link
Member Author

@hzoo - Currently babel-preset-babili is at 0.0.8 but babel-plugin-minify-dead-code-elimination is at 0.1.0, so I don't think I can just rely on the version number of the preset.

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

No branches or pull requests

2 participants