Async + WASM Plugins #73

[Polleps]

Related Issues

closes #201
closes #12
closes #1013

Checklist

• Add changelog entry linking to issue, describe API changes
• Add or update tests if needed
• Update docs if needed

[joepio]

I think we should consider merging this in even if the plugin API is still highly unstable. I now feel scared to make any substantive changes in the atomic codebase because of how many code is changed to make it async. What do you think @Polleps

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
26549932	Triggered	Generic High Entropy Secret	ab672e5	browser/lib/src/agent.test.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}