bumbler 0.8.0
“Find slowly loading gems for your Bundler-based projects”
Ruby module_eval callScript prints a CLI usage screen
SHA-256a0659f1a0a1eb07e488951d557b15574c26f8a12a8fa35e844b3b71b5c76d3cf
MaleculeH₃(DbPoU)
Evidence
14:4… # Inject our custom handling of require into the Kernel.
15 def hook_require!
16 hook_instance_require!
17 hook_singleton_require!
20:20… ance_require!
21 @hooking_instance_require = true
22
23 ::Kernel.module_eval do
24 orig_instance_require = instance_method(:require)
25 define_method(:require) do |path, *args|
26 ::Bumbler::Hooks.handle_require(path) do
27 orig_instance_require.bind(self).call(path …
56:5… # It isn't previously defined in Kernel. This could be a bit dangerous, though.
57 def self.method_added(method_name, *_args)
58 …
90:24… gem_name] = true
91
92 time, result = benchmark(path, &block)
93
94 # TODO: for items with multiple paths we need to add the times
95 Bumbler::Bundler.require_finished(gem_name, pat …
17:6… umbler shows how long loading your bundle components take.
18
19 Usage:
20 bumbler
21
22 Options:
23 BANNER
24 parser.on("-t", "--threshold MILLISECONDS", Integer, "Threshold in ms to be listed as slow") { |t| options[:threshol …
No evidence locations were recorded for this file. Raw result