-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Why "@preact/playwright-ct" types are not available? #9
Comments
Hey, does it fix itself if you add
to the package json in your node_modules, if so we are missing that field in our package. The new resolution mechanism for newer TS versions is included |
@JoviDeCroock I was checking the package.json for the node_modules>@preact>playwright-ct and that field is already inside. I tried adding |
It's not their at the first-level, only in the export-map. Mind putting it at the base level as well? |
I’m sorry @JoviDeCroock I think I'm not following, do you mean adding at the root level of my project's |
Of the package json of our package |
Like this?
|
Yes, but |
yes, that fixed it!, when is it gonna be available so I can update the package with that change? |
I mean, when someone makes a Pull Request and it gets released 😅 |
@JoviDeCroock Since you guys will add the fix for the types Issue in a next version, I'll mark this as resolved, but the problem will still present, I'll be looking forward to get this version as soon as it is available. Thanks for helping |
I tried to create a PR with the change so you guys could check it but Unfortunately I couldn’t. |
Published as 0.1.1 |
I have a project with preact and I installed the package
preact/playwright-ct
, however, Im seeing this error when importing config on myconfig.ts
file :"resource": "/playwright-ct.config.ts",
"owner": "typescript",
"code": "2307",
"message": "Cannot find module '@preact/playwright-ct' or its corresponding type declarations."
Does anyone know how to fix it? is there a missing dependency , maybe?
@developit
The text was updated successfully, but these errors were encountered: