chore: move rules_js to bzlmod

[alexeagle]

No description provided.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[fhanau]

Changes so far look good – make sure to remove the workspace imports of {rules_js, rules_ts, rules_esbuild, rules_nodejs} while we're adding the though – just grep the build/deps folder.

[alexeagle]

@fhanau done - I think the windows timeout is a flake, should I increase the timeout for that target?

[fhanau]

@fhanau done - I think the windows timeout is a flake, should I increase the timeout for that target?

This keeps timing out even after re-running – yeah, increasing the timeout might be needed here.

[github-actions]

The generated output of @cloudflare/workers-types matches the snapshot in types/generated-snapshot 🎉

[alexeagle]

Hi @fhanau this is green now, do you want to keep the timeout bump from 1min to 3min?

[fhanau]

Hi @fhanau this is green now, do you want to keep the timeout bump from 1min to 3min?

Note that the parameter is based on n seconds, not minutes. I don't think it matters much (we don't use small-sized tests much) but 1s does sound too short so let's keep it.

[alexeagle]

@fhanau can you check the red internal build? It was green before my last commit, so I don't see how I could have broken it.

[fhanau]

@fhanau can you check the red internal build? It was green before my last commit, so I don't see how I could have broken it.

Try to rebase off main. There is a failing workerd test with the downstream build, which is confusing since none of the files changed here are used by the downstream build. Only theory I have is that it didn't rebase this branch properly when running the internal-build job, so being on top of main may help? actually it's because this ran with a workerd change that requires an internal change that wasn't included yet when the job ran – any push to this should fix it.
Sorry that this keeps failing in confusing ways btw.