Ross Wollman

For generating selectors with Playwright, see also https://playwright.dev/docs/next/debug-selectors

I've pre-emptivley converted to a feature request. However, can you elaborate on your use case and why you need to XPath or CSS selector programmatically? Playwright allows you to run...

> App is so dynamic and clicking on something would make changes on DOM. I want to get all changes in form of css selectors so I can programmatically perform...

Closing per-above as part of triage. Please re-file as a feature request with the requested information about use case if this is still an issue. Thanks!

Try adding a `baseUrl` (https://github.com/microsoft/playwright/issues/7121#issuecomment-1009140849) in your tsconfig like https://github.com/rwoll/playwright-typescript-path-aliases/blob/main/tsconfig.json. Without `baseUrl` I get resolution errors, with it, the aliasing works in that linked repo.

I think the best path forward is to look at a full repro. Without it, Playwright can only guess about how the project and folder structure are interacting. I'm going...

(For above, just re-file as a new issue with the repro and reference this issue. This will ensure we see it since sometimes closed issues with later comments slip under...

Confirmed locally test passes with older npm@8, but fails after upgrade to https://github.com/npm/cli/releases/tag/v8.16.0

Upstream https://github.com/npm/cli/issues/5268

> Must be fixed for 1.25. [For now](https://github.com/microsoft/playwright/pull/16323), I will pin to last working version of `npm` for these tests. Running `npx playwright --help` outside of project works fine on...