Clarify Bundler operation

[wied03]

What happens if OPAL_USE_BUNDLER is set to true but no Bundler context is available. This situation needs to be handled. Probably need to have bundleExecute.js prepend its execSync call with bundle exec in this situation.

[cj]

@wied03 ye, I seem to be having that issue with 1.0.6. I've set OPAL_USE_BUNDLERalso externalOpal, bundler exists but it's still using the opal version that comes with opal-webpack to compile with.

[cj]

If I manually set it to true I get this:

[cj]

commenting out gem 'opal-rspec', github: 'opal/opal-rspec' in my gem spec fixes the above error

[cj]

It also gives that above error in 1.0.7 if opal-rspec is in your Gemfile.

[wied03]

I can look into it. FYI you can't use opal rspec that way though unless you
manually go load the submodules.

sent from my mobile device
On May 15, 2016 12:31 PM, "CJ Lazell" notifications@github.com wrote:

It also gives that above error in 1.0.7 if opal-rspec is in your Gemfile.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#29 (comment)

[cj]

Cheers. I'm not wanting to include opal-rspec at all, the only place it's in right now is in my Gemfile. So something else is going on.

[cj]

@wied03 if you clone https://github.com/cj/opal-connect add opal-rspec to the Gemfile run npm install && bundle && bundle exec rake webpack:run you'll see the error.

[wied03]

@cj - there might be 2 issues going on, but to expound on my short comment before, the error in your screenshot above (ruby_project) is because you can't use opal-rspec directly from Github. That's because opal-rspec submodules rspec and includes its own copy to avoid monopolizing the version of RSpec used on the MRI side.

If you want to use opal-rspec that way with opal 0.10, you'll need to bundle install, then manually go into the git repo where bundler cloned opal-rspec and do a git submodule update --init.

There probably needs to be another rubygems.org release of opal-rspec soon to avoid that, but it hasn't happened yet.

[cj]

I've tried with 0.5.0, I get the same error.