[vishnuv688]

What & why

Part of #528 and #494. Stacked on #520.

A duplicate-block scan found code repeated within and across the library packages. Each true duplicate now lives once, in the package the import rules allow; lookalikes with different purposes stay, with the reason below. No behaviour change.

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Polish (an improvement to an existing feature)
• Breaking change (existing behavior changes for users)
• Documentation
• Internal (build, CI, dependencies, tooling)

Packages touched

• shared (types and contracts)
• core (framework-agnostic capture/reporting)
• elements (published element/snapshot API — @wdio/elements)
• service (WebdriverIO adapter)
• nightwatch-devtools (Nightwatch adapter)
• selenium-devtools (Selenium adapter)
• selenium-devtools-py (Selenium Python adapter)
• backend (server)
• app (UI)
• script (page-injected runtime)
• trace (Trace mode)

Plus conformance, which the list does not include.

Capability matrix

• packages/conformance/src/features.ts updated, and tables regenerated with pnpm docs:capabilities, if this adds or changes user-facing behaviour

Not needed: no behaviour change.

Notes for reviewers

Finding	Decision
shared/element-scripts.ts: the accessibility-tree and elements page scripts each defined getAccessibleName's explicit-name steps	Shared as source text, EXPLICIT_NAME_SCRIPT, the way they already share IS_VISIBLE_SCRIPT: each script is serialized and runs in the page on its own, so they cannot share a function. Each keeps its own fallbacks
core/locators: automationName…includes('uiautomator'), five times across two files	One helper, isUiAutomatorDriver, not added to the locators index, so @wdio/elements' API is unchanged
Backend NIGHTWATCH_CONFIG_FILENAMES and Nightwatch CONFIG_FILENAMES	Moved to shared/runner.ts with WDIO_CONFIG_FILENAMES; the backend's now-empty types.ts re-export is deleted
conformance/allowlist.ts: two entries listing the same six rules for one root cause	Shared as SCRIPT_INJECTION_RULES; each entry keeps its own reason
core/locators/index.ts vs elements/locators/index.ts	Kept. Not a duplicated module: elements already re-exports core. Its explicit export list is the gate on that published package's API; export * would publish every future core export
Backend and Nightwatch upward search for a config file	Kept. They start from different places (a spec's folder, the working directory) and shared has no Node I/O

Scan for these packages: 6 blocks before, 3 after (the 3 kept above).

Why this touches an adapter: only to delete Nightwatch's copy of the config file list in favour of shared's; no adapter logic changes.

Testing

• pnpm install --frozen-lockfile, pnpm build, pnpm test (3428 passed) and pnpm lint are green; no workspace import leaks in the elements, backend, service, Selenium or Nightwatch bundles.
• New tests: 10 that run both page scripts in happy-dom over every naming source and the places they differ (they also pass on the code before this change, so they pin existing behaviour); isUiAutomatorDriver across drivers and case, and the Android vs iOS branch of getSuggestedLocators; the config file name lists.
• @wdio/elements' .d.ts files are byte-identical to before, and its export list is unchanged.

Screenshots / recordings

Not applicable: no UI change.

🤖 Generated with Claude Code