-
Notifications
You must be signed in to change notification settings - Fork 4
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
@sanity/vision
and @sanity/code-input
are both using a different version of @codemirror/state
#96
Comments
Same problem! For me, it has nothing to do with Vision. The error still appears even when I deactivate Vision. |
Same thing here: |
I don't think this has anything to do with vision. The dependency tree for
When I pin |
Could you see if upgrading to |
I have the same issue, but I'm not using @sanity/code-input in my project at all. I haven't had this issue until recently updating my dependencies with "dependencies": {
"@sanity/vision": "^3.67.1",
"react": "^18.3.1",
"react-dom": "^18.3.1",
"sanity": "^3.67.1",
"sanity-plugin-media": "^2.3.2",
"styled-components": "^6.1.13"
},
"devDependencies": {
"@sanity/eslint-config-studio": "^5.0.0",
"@types/react": "^18.3.12",
"eslint": "^9.17.0",
"prettier": "^3.4.2",
"typescript": "^5.7.2"
} |
Describe the bug
@sanity/vision
and@sanity/code-input
are both using a different version of@codemirror/state
. This is causing Sanity vision / Santiy code input plugin to throw to following error:Error: Unrecognized extension value in extension set ([object Object]). This sometimes happens because multiple instances of @codemirror/state are loaded, breaking instanceof checks.
To Reproduce
3.26.1
3.26.1
4.1.2
Screenshots
Which versions of Sanity are you using?
@sanity/code-input 4.1.2 (up to date)
@sanity/vision 3.26.1 (up to date)
sanity 3.26.1 (up to date)
The text was updated successfully, but these errors were encountered: