-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.0.0 attempts to require_relative
non-existent path
#13
Comments
I just ran into this problem too. The problem is that the rackup It seems like the
The solution is not to use |
I might recommend going so far as to pulling the |
And could we perhaps get a new release that's not broken? |
Ping. Anyway any of us could help get a fix out for this? |
Ping. |
Sorry, I have not been getting any notifications. Probably best to mention someone by name in the future if you aren't getting any traction. Let me take a look at what's gone wrong here. |
Okay, this should be fixed in v1.0.1 Yes, it's intended as a "fake" release for Rack 2.x - otherwise adding |
Problem
Attempting to
require 'rackup'
with v1.0.0 fails with:Reproduction
An example Gemfile:
after
bundle install
ing, attempingbundle exec ruby -rrackup -e 'p 42'
errors as above.Background
We're midway through upgrading our app to Rails 7.1; we now depend on Rails 7.1, but do not yet depend on Rack 3, due to a third-party dependency that doesn't support Rack >= 3. We also use Tapioca to generate RBI files. As part of the RBI generation process, the app dependencies are required, including
rackup
.The text was updated successfully, but these errors were encountered: