Raising the Bar
summary
With ~29,000 gems on RubyGems.org the practical checklist is: create a proper gemspec, put code under lib and bin, namespace everything, avoid modifying the load path, expose a single version constant in lib/<gem>/version.rb, vendor minimal dependencies, add tests and a README, wrap external errors in a gem-specific base error, and push via gem build/gem push or use Bundler’s bundle gem and rake release to automate it. Follow write gemspecs not Rake tasks and semantic versioning (MAJOR.MINOR.PATCH).
AI-written summary · about
chapters (36)
- 0:00BLUE BLUE BOX GROUP
- 1:34Choice
- 1:58Detriments
- 2:20Solution?
- 2:57Creating a Gem
- 3:31mkdir stardust cd stardust
- 5:57module Stardust end
- 7:44VERSION = '0.0.1'
- 9:52gem build stardust.gemspec
- 10:45Dependencies
- 11:36gem install stardust -0.0.1.gem --development
- 12:06A Gotcha
- 12:46Bundler
- 13:40bundle gem stardust
- 14:31Rake Tasks
- 14:56rake install
- 15:21Write Tests!
- 15:36test/ spec
- 16:16Read Tests!
- 16:37Defining Conventions
- 18:13require 'rubygems'
- 19:16Error Handling
- 20:21Testing
- 20:49Packaging
- 21:39Versioning
- 22:09Public API
- 22:37Immutable
- 24:29Community Contributions
- 25:00Contribution Policy
- 25:19Bumping Versions
- 25:46State of the Ecosystem
- 26:14gem push
- 26:40Gem or Custom?
- 27:02Duplicates?
- 27:55barriers
- 28:52Questions
