Ruslan Lesiutin 67a05d03e3 fix[devtools]: fixed duplicated backend activation with multiple renderers (#26807) ...

## Summary
Initially reported in https://github.com/facebook/react/issues/26797.
Was not able to reproduce the exact same problem, but found this case:

1. Open corresponding codepen from the issue in debug mode
2. Open components tab of the extension
3. Refresh the page

Received multiple errors:
- Warning in the Console tab: Invalid renderer id "2".
- Error in the Components tab: Uncaught Error: Cannot add node "3"
because a node with that id is already in the Store.

This problem has occurred after landing a fix in
https://github.com/facebook/react/pull/26779. Looks like Chrome is
keeping the injected scripts (the backend in this case) and we start
backend twice.

2023-05-12 14:59:53 +01:00

..

contentScripts

[DevTools] use backend manager to support multiple backends in extension (#26615)

2023-04-18 12:02:42 -04:00

backend.js

fix[devtools]: fixed duplicated backend activation with multiple renderers (#26807)

2023-05-12 14:59:53 +01:00

backendManager.js

fix[devtools]: fixed duplicated backend activation with multiple renderers (#26807)

2023-05-12 14:59:53 +01:00

background.js

DevTools: fix backend activation (#26779)

2023-05-04 17:34:57 +01:00

main.js

[DevTools] use backend manager to support multiple backends in extension (#26615)

2023-04-18 12:02:42 -04:00

panel.js

Enable prefer-const lint rules (#18451)

2020-04-01 12:35:52 -07:00

utils.js

[DevTools] use backend manager to support multiple backends in extension (#26615)

2023-04-18 12:02:42 -04:00