The git tags and gem versions keep in sync with LiveScript compiler version it provides.
But with one exception: the
Since rubygems.org doesn't allow re-push a version, and doesn't support release number, there is no way to fix bugs or add new features without breaking the version consistency with LiveScript. We use
rc as release number to solve this problem.
Each time LiveScipt releases a new version, say 1.4.0, we will release this gem as
1.4.0.rc.1. When bugs are fixed or new features are added, we'll release a new version of
1.4.0.rc.2, and then
It's used as a dependency by livescript gem.
It's not recommended to install it directly.
Instead, install livescript, and it will pick up an appropriate version of this gem to install.
# update LiveScript source file ./update [VERSION] # test bundle exec rake test # push to rubygems.org gem push livescript-source-[VERSION].gem
VERSION should be tags in gkz/LiveScript.
- Fork it ( http://github.com/Roonin-mx/livescript-source/fork )
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Add some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request