Typescript types not available

[FilipChalupa]

Maybe because 61f31b7 is not released yet.

[noamr]

I released it now (sorry, was off-grid for a while).

[FilipChalupa]

I'm not sure it works properly. Npmjs.org still shows no [TS] badge and neither can I get types to work in my project.

@vkuprin there should be "types": "…" in package.json which is missing, right?

No badge

Other repository with the badge

[vkuprin]

@FilipChalupa The cleaner approach would be to rewrite everything in types and eliminate .js files altogether. Relying on declaration files can lead to some problems with package types, as we've seen. I will make a patch soon to cover everything in TypeScript. Please bear with me

[vkuprin]

@FilipChalupa @noamr Please take a look at my patch #7
With npm run build:packages it should create a dist folder with .js files

[FilipChalupa]

@vkuprin thank you for your quick response. 🙂 I'm worried that the changes will complicate use without TypeScript. May I suggest an edit? Something like this: vkuprin#1. It's not perfect. I've been forced to place a few @ts-ignore and I'm not completely sure that types will be picked up from exports.*.types but I believe it is a step in right direction. 🤷‍♀️

[vkuprin]

@FilipChalupa Merged your changes! Good point. It's not perfect, but we are gradually improving our hook. Adding test coverage with something like Jest could potentially be our next steps

[vkuprin]

@noamr The last CI pipe has failed. Please redeploy or let's push to the master .lock files to avoid pipeline failures. Right now, it's an old version

[williamisnotdefined]

Meanwhile I have created a .d.ts with the following statement:
declare module "use-view-transitions/next";

it made the vscode stop complaining about the library installation, hope it work for you guys