BETAmodules.com is in beta — open to partnerships & joint ventures.Build with us

wad

v0.2.1RubyGems· Ruby

Since we're all following very strict standards with regards to how our gems are constructed, we might as well pack all those gems back into a directory and use that directory in our load path. Once you do that, you'll discover that loading from all these paths and doing dependency resolution cost on every ruby invocation. On our machines, using wad saves us >500ms every time, on every call. Wad helps you with getting there: It vendors your Gemfile below `vendor/bundle`, then copies relevant source code to `vendor/lib`. All in one simple call.

The verdict
Abandoned. Last published 11 years ago. No recent activity — look for a maintained alternative.
No recent activity — look for a maintained alternative.
Live from the RubyGems registry · derived rules, not AI
How it scores
MaintenanceAbandoned
PopularityNiche
SecurityClean
LicensePermissive
DepsZero deps
Maintenance
Last published 11 years ago.
Popularity
8 downloads / week
Security
No known advisories for this version (OSV).
License
MIT
Dependencies
No runtime dependencies
Recent releases
  • 0.2.111 years ago
  • 0.2.011 years ago
wad — Since we're all following very strict standards with regards to how our gems are constructed, we might as well pack all those gems back into a directory and use that directory in our load path. Once you do that, you'll discover that loading from all these paths and doing dependency resolution cost on every ruby invocation. On our machines, using wad saves us >500ms every time, on every call. Wad helps you with getting there: It vendors your Gemfile below `vendor/bundle`, then copies relevant source code to `vendor/lib`. All in one simple call. (Ruby / RubyGems) · Modules