Add exports.types to package.json

[yuhgto]

Added the types file path to exports.types in package.json to prevent the following error:

Could not find a declaration file for module '@mondaycom/apps-sdk'. '/Users/diprobhowmik/Documents/Development/monday-code-demo/next-js-typescript-test/node_modules/@mondaycom/apps-sdk/dist/esm/index.js' implicitly has an 'any' type.
  There are types at '/Users/diprobhowmik/Documents/Development/monday-code-demo/next-js-typescript-test/node_modules/@mondaycom/apps-sdk/dist/types/index.d.ts', but this result could not be resolved when respecting package.json "exports". The '@mondaycom/apps-sdk' library may need to update its package.json or typings.

The reason behind this error is that node will ignore the types field if the package has an exports field. And since the exports didn't include an exports.types, node would not be able to find the relevant types .

Docs & stackoverflow here –
https://stackoverflow.com/a/76212193
https://www.typescriptlang.org/docs/handbook/esm-node.html#packagejson-exports-imports-and-self-referencing

[yuhgto]

closing because its stale

[yuhgto]

Hey, reopening this because someone brought it up again in the dev community.

We are using an outdated package.json structure: as of Typescript 4.7, the types field in package.json will no longer be used. We need to move the types field under exports

See this StackOverflow - https://stackoverflow.com/questions/76211877/the-xxxx-library-may-need-to-update-its-package-json-or-typings-ts/76212193#76212193

[DorShakedMonday]

Based on the stackoverflow link you have provided, the types should be first inorder.
This sounds like a myth, but won't hurt to make it first in the declaration order