You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 00d187e
Browse filesBrowse the repository at this point in the historyBrowse files
feat(devtools): add hideInAutomation to keep devtools out of e2e tests
With plugins open by default, end-to-end tests that select elements by id
or text also matched the devtools panels. The workarounds were turning off
defaultOpen for every plugin or hiding #tanstack_devtools with CSS.
`hideInAutomation: true` skips the devtools DOM when navigator.webdriver is
true, which Playwright, Cypress, and Selenium set. Local development does
not change. The default is false, so suites that test the devtools
themselves keep working.
Fixes#318
Add the `hideInAutomation` config option. When it is `true`, the devtools do not render in a browser that automation drives (Playwright, Cypress, Selenium), detected by `navigator.webdriver`. This keeps the devtools out of end-to-end test selectors. The default is `false`.
-`hideInAutomation` - Does not render the devtools when a browser is driven by automation (Playwright, Cypress, Selenium). This keeps the devtools out of your end-to-end test selectors. The check uses `navigator.webdriver`. The default is `false`.
75
+
76
+
```ts
77
+
{ hideInAutomation: boolean }
78
+
```
79
+
74
80
-`triggerImage` - The image used for the dev tools trigger
0 commit comments