## Summary
resolves #24522
To upgrade to Manifest V3, one of the biggest issue is that we are no
longer allowed to add a script element with code in textContent so that
it would run synchronously. It's necessary for us because we need to
inject a global hook for react reconciler to detect whether devtools
exist.
To do that, we'll leverage a new API
`chrome.scripting.registerContentScripts` in V3. Particularly, we rely
on the "world" option (added in Chrome v102
[commit](
|
||
|---|---|---|
| .. | ||
| README.md | ||
| build.js | ||
| deploy.js | ||
| manifest.json | ||
| now.json | ||
| test.js | ||
README.md
The Chrome extension
The source code for this extension has moved to shells/webextension.
Modify the source code there and then rebuild this extension by running node build from this directory or yarn run build:extension:chrome from the root directory.
Testing in Chrome
You can test a local build of the web extension like so:
- Build the extension:
node build - Follow the on-screen instructions.