ActionCable npm package renamed about stimulus_reflex HOT 4 CLOSED

@dark-panda can you tell us what the error was?

from stimulus_reflex.

@hopsoft I feel like this needs to be flagged as high priority

from stimulus_reflex.

Error connecting controller

TypeError: Error connecting controller - TypeError: this.getConfig is not a function
    at createConsumer (action_cable.js:24)
    at T (consumer.js:27)
    at stimulus_reflex.js:49
    at Object.ie [as register] (stimulus_reflex.js:149)
    at t.value (info_controller.js:8)
    at e.connect (context.js:18)
    at e.connectContextForScope (module.js:34)
    at e.scopeConnected (router.js:80)
    at e.elementMatchedValue (scope_observer.js:42)
    at e.tokenMatched (value_list_observer.js:44)

Which in its pre-compiled form looks something akin to this:

https://github.com/rails/rails/blob/d03177ffbccb5b30217448d526f1e9aa1fa24297/actioncable/app/javascript/action_cable/index.js#L22

Or compiled:

createConsumer: function(url) {
  var ref;
  if (url == null) {
    url = (ref = this.getConfig("url")) != null ? ref : this.INTERNAL.default_mount_path;
}

It appears that it's using its dependency version of ActionCable 5.2.4, but since I upgraded to Rails 6 I'm using ActionCable 6.0.2.2 via the @rails/actioncable package. I could potentially downgrade or remove that package and just use the 5.2.4 version, but I'm not sure how that would play with the server version. Presumably what's going on here is that I've initialized with the 6.0 version of ActionCable while Stimulus Reflex is using its own version, and the two aren't playing nice. You should only be using one version of ActionCable at any given time.

from stimulus_reflex.

Resolved by #135

from stimulus_reflex.