replace-jquery VS awesome-actions

This might be worth checking out: https://github.com/sachinchoolur/replace-jquery

- It seems to have subtle bugs, like the way the events string is split makes so that double consecutive spaces in it (which can happen as a result of a typo) will result in listening to the empty string event. Basically: 'foo bar'.split ( ' ' ) => ['foo', '', 'bar'].

The `on` method we are using in Cash [1] is a lot more convoluted than that. On one hand it requires more bytes, but on the other the chances of it behaving exactly like jQuery's are much higher. In fact we can also run jQuery's test suite with Cash to spot issues.

Feel free to ping me if you are interested in joining forces.

[0]: https://github.com/fabiospampinato/cash

[1]: https://github.com/sachinchoolur/replace-jquery#on

[2]: https://github.com/fabiospampinato/cash/blob/master/src/even...

Show HN: Auto-generate vanilla JavaScript alternatives for jQuery methods\ (0 comments)

Awesome Actions - A curated list of awesome things related to GitHub Actions.

Since it sounds like you're using GitHub, using GitHub Actions for any CI pipelines would be easiest. You could run terraform plan in your PRs, there's a great writeup on how to do it here. Or any unit tests, docker builds, etc. Lots of great ideas at Awesome Actions.

Here is a list of some examples you might want to check out.

A curated list of actions to use on GitHub\ (6 comments)

With the recent success of Github actions you can automate lots of things whenever something in your repos changes, e.g. automatically generate static HTML content (using hugo) and push it to some repository for which GitHub Pages has been configured. Check this awesome actions list for more use cases.

Projects: awesome-actions, intro-to-vue, cssgridgenerator, array-explorer, ecommerce-netlify