You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 20, 2021. It is now read-only.
hotwire-rails installs stimulus-rails, which was designed exclusively for use with the asset pipeline. It doesn't make sense to run stimulus:install, if the app is using Webpacker. So detect and skip that.
(This essentially means that if you're not using the asset pipeline, you can just use the turbo-rails gem directly. But I could see people following tutorials and missing this part.)
The text was updated successfully, but these errors were encountered:
Actually, even better, we should upgrade stimulus-rails to have a stimulus:install task that adds stimulus to package.json if it isn't already. Ala webpack:install:stimulus. Going to do that instead.
Actually, even better, we should upgrade stimulus-rails to have a stimulus:install task that adds stimulus to package.json if it isn't already. Ala webpack:install:stimulus. Going to do that instead.
Is there an issue I might subscribe to for tracking this? Thanks for your work on this. Nevermind, I now see #17.
Just hit a Error: Cannot find module 'controllers' error when using the hotwire-rails gem on a default Rails app. Does that mean we should bypass hotwire-rails in this case?
hotwire-rails installs stimulus-rails, which was designed exclusively for use with the asset pipeline. It doesn't make sense to run stimulus:install, if the app is using Webpacker. So detect and skip that.
(This essentially means that if you're not using the asset pipeline, you can just use the turbo-rails gem directly. But I could see people following tutorials and missing this part.)
The text was updated successfully, but these errors were encountered: