good-first-issue VS _hyperscript

First Contributions, EddieHub Issue Finder, goodfirstissue.dev, goodfirstissues.com, firsttimersonly.com.

https://goodfirstissue.dev might be a great place to check :)

Another source is mentor feedback, somebody who tells you he thinks you can do it, some projects seem more open to new contributors, search good first issue, if you will open an issue saying you are willing to commit to say 1-2h a week for a year i believe you will get help.

Good First Issue

Good First Issue website curates the issues with good first issue tag from various open-source projects and displays them with a nice and clean UI.

If that doesn't work, get on https://socialcoder.org/Home/Index or contribute to an open source project - https://goodfirstissue.dev/.

OSS contributions: https://goodfirstissue.dev/

You can also use websites like up-for-grabs, goodfirstissue, or CodeTriage to find projects with open issues. Find one that looks easy or interesting to you and comment on it, asking if you can take a shot at it.

It seems to be this one:

https://github.com/bigskysoftware/_hyperscript

https://hyperscript.org/

but no sure it's anything to do with the OP though

You could help hyperscript get to a stable 1.0 by reading docs and writing up some use cases if you know anything about front end web development

If we returned from a function, we step out of it (discussed below). Otherwise, if the command returned a Promise, we await the next command, set cmd to it, notify the event bus and log it with some fancy styles. If the result was synchronous and is a HALT; we stop debugging (as I write this, I'm realizing I should've called continueExec() here). Finally, we commit the kind of code duplication hyperscript is meant to help you avoid, to handle a synchronous result.