fix(FaceLandmarker): default basePath aligned with tasks-vision package version

[abernier]

Why / What

In FaceLandmarkerDefaults.basePath the version was until now hardcoded: 0.10.0

drei/src/core/FaceLandmarker.tsx

Line 16 in 93d779d

basePath: 'https://cdn.jsdelivr.net/npm/@mediapipe/tasks-vision@0.10.0/wasm',

This PR lets use @rollup/plugin-replace(compatible with Vite) to make it dynamic, with the version of the installed @mediapipe/tasks-vision package

Checklist

• Documentation updated (example)
• Storybook entry added (example)
• Ready to be merged

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
drei	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 21, 2023 9:17am

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 046b888:

Sandbox	Source
aged-sun-44m5z7	Configuration
Ground reflections and video textures	Configuration
arc-x-pmndrs-colors	Configuration

[abernier]

this is the purpose replacement of this PR

[abernier]

@rollup/plugin-replace is compatible with Vite

[abernier]

let you review @CodyJasonBennett since it touches rollup.config.js and is related to @mediapipe/tasks-vision bump from #1509

[CodyJasonBennett]

This relies on pinning the version so we can't use loose ranges via ^ and ~ since they get resolved by users' package managers. We currently do this since they publish RCs in a weird way without pinning, but it prevents this from working dynamically.

[abernier]

This relies on pinning the version so we can't use loose ranges via ^ and ~ since they get resolved by users' package managers. We currently do this since they publish RCs in a weird way without pinning, but it prevents this from working dynamically.

In my mind we can use any ranges since it reads the version directly from node_modules/@mediapipe/tasks-vision/package.json.version which is necessarily resolved by the package manager.

I've checked with our currently defined 0.10.2-rc2 that the files were here at the dynamically printed basePath https://cdn.jsdelivr.net/npm/@mediapipe/tasks-vision@${"0.10.2-rc2"}/wasm

[seungwoohong]

I have this issue.
does this have anything to do with this error?