@wolfv, I'd siggest to search and go over existing tickets/PRs related to JavaScript port, and post links to this PR, because likely many people interested in that stuff are not aware of this new development.

Thanks @wolfv for picking this up. I'm happy to merge this now, except for one item: what was your reason to remove the JSBackend.patch file? AFAIK it's still needed, and also referenced from the README.md (with explanation on why it's needed).

@dpgeorge you're right! I just reverted removing the patch. I also checked, and it does seem like a useful patch (even though I did not have to apply it for my simple tests).

It would be great if this was merged. I have some additional features that I would put in a next PR. (e.g. a javascript module that allows eval-ing JS code from MicroPython,

@wolfv in your single commit there are 2 lines in extmod/moduselect.c that are changed. These should go in a separate commit to be able to more easily track changes to the core and ports separately. I can do this myself during the merge of this PR (the commit would be authored by me, but I'd acknowledge you in the commit message), or you can split it out yourself here in this PR (so there'd be 3 commits in total in this PR). Let me know what you'd prefer.

I'll remove it from this PR, check if it still builds fine, and then create a seperate PR.

I had to remove -Werror -Wall flags from the CCFLAGS but then it still builds. Will open another PR.

opened a seperate PR #4601

I guess this is good to go in now that #4601 is merged?

I could re-add the warning flags? otherwise, yes!

i think it's fine to merge as-is, I will open a next PR with more features and re-add the flags there.

I could re-add the warning flags?

Yes, it would be best not to remove them, so please undo that change.

done and rebased.

Thank you very much! Merged in 7d675f3 and ea2fcdd