stimulus-rails VS Whenever

https://github.com/hotwired/stimulus-rails I think you need to understand how rails works because it clearly says I’m right here buddy

So I've been following the setup for https://github.com/hotwired/stimulus-rails with using the importmap, tried to get @hotwired/stimulus-loading pinned and its stating that it no longer exists...

Thanks! Now I learn 'named export' keyword... Could your show the code of named export? I searched but I don't find the one. I thinks this issue is what you say but I don't get it.

- [stimulus-rails](https://github.com/hotwired/stimulus-rails)

stimulus-rails

The tricky part of recreating the disable behavior is getting the interface to be as clean as the original. I actually opened a PR regarding a disable controller earlier this year, and the man himself said as much about the interface (I embarrassingly left the PR stale after getting swept up in my last semester of college).

The Stimulus Handbook

Have you checked out the stimulus-rails gem? It sounds like it will let you stop manually registering controllers, and use the normal ES6 import syntax for inheritance:

Run `hotwire:install Hotwire also has the following resources available: Hotwired Turbo Rails Hotwired Stimulus-rails

There's an open issue about it: https://github.com/hotwired/stimulus-rails/issues/15

Learn about Unix cron and use the whenever gem.

there are cronjob gems available, i believe https://github.com/javan/whenever or so seems to be used frequently

- Use them on a specific schedule as needed by your application, such as taking backups, sending periodic reminders or notifications for users, cleaning the database tables, etc. You can use a gem such as Whenever for managing scheduled cron jobs.

whenever gem is used in Rails applications to schedule cron jobs e.g. send email notification about monthly expenditure on the 1st of each month.

Then you can use the whenever gem to schedule stuff.

- [whenever](https://github.com/javan/whenever)

whenever

There are multiple ways to achieve this. Probably the simplest and most reliable is to rely on cron to run your process every minute. Cron keeps track of time and executes your script each minute. This has the added benefit of avoiding a long running process (which can have its own issues). You can even have your script install it’s own cron job using the Whenever gem.

Rake tasks can be called from Cron, so we'll use the Whenever Gem to automatically add our job to our Crontab during deployment, and keep our schedule in change control.