When installing breakfast, node and npm are checked for existence but not for a correct version. The Breakfast Installation will proceed and running the server will give a cryptic error message that eventually results from using an old NPM version (possibly Node as well?).
Here is a possible solution to check for satisfactory node/npm versions. The specific versions are based on my ability to successfully run a server with a react component using breakfast.
I lost the exact error, but it might have been either
$ bin/rails s
=> Booting Puma
=> Rails 5.0.0.1 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
Exiting
/Users/Josh/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/breakfast-0.1.1/lib/breakfast/railtie.rb:26:in `spawn': No such file or directory - brunch (Errno::ENOENT)
from /Users/Josh/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/breakfast-0.1.1/lib/breakfast/railtie.rb:26:in `block in <class:Railtie>'
or
E, [2016-09-11T11:41:03.412038 #1584] ERROR -- : exception while processing events: undefined method `fetch' for nil:NilClass Backtrace:
-- /Users/Josh/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/actioncable-5.0.0.1/lib/action_cable/server/configuration.rb:24:in `pubsub_adapter'```
PatKoperwas
commented
8 years ago
When installing breakfast, node and npm are checked for existence but not for a correct version. The Breakfast Installation will proceed and running the server will give a cryptic error message that eventually results from using an old NPM version (possibly Node as well?).
Here is a possible solution to check for satisfactory node/npm versions. The specific versions are based on my ability to successfully run a server with a react component using breakfast.
I lost the exact error, but it might have been either
or