Saskia Bobinska
Senior Support Engineer @Sanity
Saskia is located at Berlin Germany
What to do when Studio crashes due to conflicts in dependency versions?
If you install plugins or other packages with conflicting (peer) dependencies, you can use this useful workaround to unblock yourself.
Add the flag to your npm install command
npm i <package name> --legacy-peer-deps
Sometimes, when we update the studio to use a newer version of a package (with breaking changes to an older version), your studio can crash if the same package is used in an older version in plugins or custom tools, etc. (see this example on GitHub).
In these cases, you don't have to panic, stay on the studio's older (minor) version, or uninstall the plugin or tool. 😮💨
You can simply:
- File an issue in the plugin to update the dependencies to the newer version of the package in case (like
styled-components) - Reinstall the plugin using the peer-legacy flag in NPM
--legacy-peer-deps
If this does not work, you might need to remove your node modules, delete your lock-file, and reinstall everything using the flag again.
Happy coding!
Contributor
Other recipes by the contributor
Resolve-to-Publish: Comments based publish action
A custom publish action that opens the comments inspector instead of publishing if unresolved comments exist
Saskia Bobinska
Update references via Content Migration script
Use a migration script to update all references from one document to another
Saskia Bobinska
Use the validation status of a document in your custom document actions
When creating custom document actions, it can be necessary to check, wether all validation rules are full-filled.
Saskia Bobinska
Conditional values in GROQ queries
Only return a value when a condition is fulfilled
Saskia Bobinska