@mediapipe/tasks-vision include types exports in package.json

[KostisP]

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)

No

OS Platform and Distribution

javascript

MediaPipe Tasks SDK version

No response

Task name (e.g. Image classification, Gesture recognition etc.)

all

Programming Language and version (e.g. C++, Python, Java)

javascript 0.3.10

Describe the actual behavior

Typescript cannot find a declaration file for @mediapipe/tasks-vision module.

Describe the expected behaviour

`"types": "./vision.d.ts" ` should be added under exports in package.json

`
"exports": {
    "import":  "./vision_bundle.mjs",
    "require": "./vision_bundle.cjs",
    "default":  "./vision_bundle.mjs",
    "types": "./vision.d.ts" 
  }
`

Standalone code/steps you may have used to try to get what you need

import { FaceLandmarker } from '@mediapipe/tasks-vision';

Other info / Complete Logs

No response

[zoeleu]

Just now faced this issue.

[kiochan]

@KostisP Here is a temporary solution for this issue.

In your tsconfig change moduleResolution to node. This solution will force typescript compiler to read types from the root of package.json file.

{
  "compilerOptions": {
    "moduleResolution": "node",
  }
}

[schmidt-sebastian]

Will add this. Should be part of next release.

[google-ml-butler[bot]]

Are you satisfied with the resolution of your issue? Yes No

[sunapi386]

Take a look at this issue https://stackoverflow.com/questions/66096260/why-am-i-getting-referenceerror-self-is-not-defined-when-i-import-a-client-side

In short, the error occurs because the library requires Web APIs to work, which are not available when Next.js pre-renders the page on the server-side.

[zoeleu]

Take a look at this issue https://stackoverflow.com/questions/66096260/why-am-i-getting-referenceerror-self-is-not-defined-when-i-import-a-client-side

In short, the error occurs because the library requires Web APIs to work, which are not available when Next.js pre-renders the page on the server-side.

No. I faced this issue outside of Next.js.