Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vision 3.79.0 fails to: "No matching export for EditorSelection" #8917

Closed
jorngeorg opened this issue Mar 13, 2025 · 2 comments · Fixed by #8998
Closed

Vision 3.79.0 fails to: "No matching export for EditorSelection" #8917

jorngeorg opened this issue Mar 13, 2025 · 2 comments · Fixed by #8998
Assignees

Comments

@jorngeorg
Copy link
Contributor

Sanity studio with Vision 3.79.0 fails to build due to this error

✘ [ERROR] No matching export in "node_modules/@uiw/react-codemirror/esm/index.js" for import "EditorSelection"

    node_modules/@sanity/vision/lib/_chunks-es/SanityVision.mjs:10:21:
      10 │ import CodeMirror, { EditorSelection } from "@uiw/react-codemirror";

Downgrading to 3.78.0 fixes the problem.

sanity versions
@sanity/cli (global)          3.72.1 (latest: 3.79.0)
@sanity/eslint-config-studio   5.0.1 (latest: 5.0.2)
@sanity/locale-nb-no          1.1.19 (up to date)
@sanity/types                 3.79.0 (up to date)
@sanity/ui                    2.15.2 (latest: 2.15.6)
@sanity/vision                3.79.0 (up to date)
@julianCast
Copy link

Exactly, it causes the build to fail.

@pedrobonamin
Copy link
Contributor

I'm sorry for the inconvenience, this is a dependencies miss match on our side, thank you for reporting it.

We are declaring in the vision package to use ^4.19.9 and that is resolving to the version 4.23.8 which exports the EditorSelection, but version 4.19.9 doesn't export it 🤯

Opening a Pr that should fix this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants