Types exported from playwright-core, but not playwright
See original GitHub issue// this works
import { ElementHandle } from "playwright-core";
// this does not
import { ElementHandle } from "playwright";
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Advanced: configuration | Playwright - CukeTest
It must export a single function. globalTeardown: string - Path to the global teardown file. This file will be required and run after...
Read more >How To Run End-to-End Tests Using Playwright and Docker
In this tutorial, you will set up an environment to use Playwright with Typescript for end-to-end testing, write and execute the tests, export...
Read more >React + Typescript + Playwright , Module Not found
I am using React, Typescript and I want to create a web scraper using Playwright. My code is: const playwright = require('playwright'); ...
Read more >playwright-elements - npm
Playwright elements helps you to create reusable components and allows lazy initialization. ... IMPORTANT: playwright elements is not standalone ...
Read more >fix(playwright-test): have the proper default export (#7328)
Also, typescript types import from `.d.ts` file was broken because we had no default export (`export *` syntax does not export default). pull/7331/head....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks @jperl! Collecting typing issues around specific methods is great, and any PRs are welcome. However, we plan to work on types soonish (probably hand-written
.d.ts
file), so general improvements like re-exporting types between packages will be probably lost during transition.We can have different defaults externally vs internally (e.g.
ElementHandle
wrappingHTMLElement
by default), have short documentation attached to be shown in IDEs, and not pollute types with internal methods starting with underscore.