3 Matching Annotations
  1. Jun 2021
    1. You need to run gem pristin --only-executables Because whenever a ruby is updated or perhaps moved/named, due to RubyGems is generating explicit #!/path/to/ruby for all gem executables, will need to regenerate the gem bin stubs with the new path to the ruby executable.
  2. Dec 2019
    1. Please don't name binstubs common executable names. It just creates a whole bunch of shadowing issues. Granted, I also have an npm issue at hand, but I do think naming your binstubs webpack and webpack-dev-server is asking for trouble. Why not webpacker and webpacker-dev-server?
    2. The global executables are removed in latest release.