Closed bigwheel closed 1 year ago
Im understanding why this happens.
$% cat ~/.bundle/config
---
BUNDLE_PATH: "vendor/bundle"
https://github.com/tongueroo/jets/blob/0df7fc93/lib/jets/commands/new.rb#L65-L87
bundle install
executes with BUNDLE_IGNORE_CONFIG
, but bundle exec jets webpacker:install
does not.
This could be considered as my environment problem. But it seems like BUNDLE_IGNORE_CONFIG
inconsistency problem.
I hit this same issue. I worked around the issue by temporarily commenting out the contents of ~/.bundle/config .
Me too.
Thank you for the hints, as I was using Cloud9, I had to remove my personal ~/.bundle/config
, install and use Ruby 2.7 and install latest bundler to get it to work.
it could help if it was supported to add jets
to our Gemfile
stall
Checklist
jets upgrade
command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/My Environment
Expected Behaviour
Success of
jets new demo
Current Behavior
Fails on the way.
Detail: jets_new_log
Step-by-step reproduction instructions
I do just Quick Start - Jets Ruby Serverless Framework.
jets new demo
Code Sample
jets new demo
Solution Suggestion
This may be a matter of dependency declaration.