| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@nodejs/modules-active-members |
Sorry, something went wrong.
There was a problem hiding this comment.
minor nits, but seems like a good PR
Sorry, something went wrong.
|
Rebased against master, resolved conflicts, force-pushed. PTAL |
Sorry, something went wrong.
Sorry, something went wrong.
|
@Trott I had originally split the PR in two commits, one for the change in the evalModule signature (0268ed72d894970f6a0011fd6bfa8203d42db0fe), one to actually add support for the data: URLs (28eedafd6a78d95f9860c78aa4f77e191a026e99). If we want to squash into one commit, I think the commit message should be taken from the latter rather than the former. What are your thoughts? EDIT: turned out 0268ed72d894970f6a0011fd6bfa8203d42db0fe is no longer necessary thanks to e948ef3. I've removed it in my last force push. |
Sorry, something went wrong.
Works for me. Want to make the change and force-push? Sorry I squashed when perhaps I shouldn't have. Feel free to split it back into two commits, if that's what you prefer and if it's not a big hassle. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Possibly related error in CI? Same test failed on two platforms |
Sorry, something went wrong.
|
Jenkins is a bit confusing to me, which test do you say is failing? From what I can see, there are two: Again, this is a bit obscure to me, but they don't look related to this PR. |
Sorry, something went wrong.
|
Heh, you're right, there are two separate ones. I likely ended up looking at the same results twice. Either way, we just need a quick confirmation that they are unrelated and to run them again to doublecheck. They might be flaky tests. |
Sorry, something went wrong.
Sorry, something went wrong.
|
CI still unfortunately flaky. Running again |
Sorry, something went wrong.
|
CI is green 🥳 |
Sorry, something went wrong.
PR-URL: #34584 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Bradley Farias <bradley.meck@gmail.com> Reviewed-By: Jan Krems <jan.krems@gmail.com>
PR-URL: #34584 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Bradley Farias <bradley.meck@gmail.com> Reviewed-By: Jan Krems <jan.krems@gmail.com>
PR-URL: #34584 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Bradley Farias <bradley.meck@gmail.com> Reviewed-By: Jan Krems <jan.krems@gmail.com>
| Back | FazBrowse Home | New Git URL |
This PR adds support for data URLs using the same implementation provided by the ESM implementation. This covers the use case of a user wanting to use eval in a worker thread with ESM syntax.
Checklist