fix(plugin-recaptcha): Enhance esbuild transpilation support of content scripts #763
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR builds on #758
It also fixes a fix to workaround
esbuild
's__name
semantics: privatenumber/tsx#113The author of
esbuild
recommends against callingtoString()
on a function or class as this library is doing and instead creating a separate build for these entrypoints. This results in a lot more deterministic functionality, but that would also involve a larger PR.So for now, this is the minimal amount of code changes to get
puppeteer-extra-plugin-recaptcha
's injected content scripts to work when used in an application that's compiled usingesbuild
.I ran into this issue while building the chatgpt node.js wrapper, which uses uses
tsx
to transpile TS to JS on-the-fly (usingesbuild
under the hood).Also just wanted to say hey @berstend 👋 I remember working with you a bit years ago back in the early days of this project. Really really impressive to see how far it's come 🔥
Thanks for all your hard work && cheers,
-- Travis