Possible install instruction change needed for Webpacker 6 about turbo-rails

[javan]

Does this "fix" it?

- import { Turbo, cable } from "@hotwired/turbo-rails"
+ import "@hotwired/turbo-rails"

[dhh]

Sounds like Webpack is shaking its tree and not finding any usages of Turbo in the pack itself. @javan any idea how we might stop this from happening? Maybe with Webpack we shouldn't have the lib call start() itself.

[styrmis]

I'm experiencing the same with webpacker 5.1.1. To get around it I've added a Turbo.start() call after the import, as it looks like this should have no effect beyond persuading Webpack to keep Turbo in the tree.

I'm only using javascript_pack_tag, not javascript_packs_with_chunks_tag.

[styrmis]

Does this "fix" it?

- import { Turbo, cable } from "@hotwired/turbo-rails"
+ import "@hotwired/turbo-rails"

Yes, this works fine.

[noelrappin]

Yeah that worked for me under Webpacker 6 beta also.

[chmich]

Thanks, same for vite

For Turbo itself, this was not necessary, but ActionCable only worked in this way.