[package.json] add types in exports field

[thibthib]

Starting from TS 4.7 (see release note), we need to add a types field in the exports object when then path to the .d.ts file doesn’t match the file exposed.

If it isn’t set, we have the following error:

There are types at '[...]/node_modules/yaml/dist/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'yaml' library may need to update its package.json or typings.

This should fix it by adding the same types as top level, but within the exports object

[tal-rofe]

@thibthib The issue occurs to me also. Is there WA in the mean time?

[eemeli]

Thank you! Had not noticed the TS update on this, and the proposed change looks just like should.

[thibthib]

@tal-rofe The only workaround is to patch the library locally, and it will widely depend on the package manager you are using.

@eemeli Thanks for the review ! Do I need to do anything else to see this change in a new version of the library ?

[Ayc0]

patch the library locally, and it will widely depend on the package manager you are using.

With yarn 2+ you can use the patch: protocol (link), with pnpm you can use patchedDependencies (link), and with npm you can use the package patch-package

[eemeli]

@eemeli Thanks for the review ! Do I need to do anything else to see this change in a new version of the library ?

No need for further action from you. I'll release a new prerelease version shortly.

[eemeli]

There was an incompatibility with the typesVersions as well, which had been an attempt at fixing the types for the 'yaml/util' endpoint. The types should now work as intended with yaml@2.3.0-3.

[thibthib]

Thanks a lot @eemeli !