-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
1.0.0.beta1 requires 'pry' but it's a development dependency #405
Comments
Thx for the catch. The fix is on master branch, still haven't released beta2. Please use mina directly from github as beta1 is broken. |
Thanks, but the master branch does not work at the present:
|
Nice catch. |
seem that the dependencies are not loaded; getting |
I faced @bbnnt bug too. When will this be fixed? |
we have released beta2. Please use that |
@d4be4st version 1.0.0.beta1 is required when install |
Updated gempec for mina-npm, you should be able to use beta2 now |
Reproduced in Any way to require 1.0.0.beta1 and 1.0.0.beta2 both have severe bugs and are not working properly. Maybe it is caused by the lack of test? Currently I may not be able to contribute code to |
I tried to use mina 1.0.0.beta1 in a Rails 4.2.7 project, but
bundle exec mina init
failed with:According to mina.gemspec,
pry
is a development dependency, but it is required inlib/mina.rb
.If I add
pry
to myGemfile
,bundle exec mina init
will report another error:It seems that this bug has been fixed in master branch.
But the master branch does not work now, it will report some other errors.
Hopes a working beta release coming soon.
After all, mina is an excellent tool for simple deployment. Thanks for your hard work!
The text was updated successfully, but these errors were encountered: