Duplicate plugin "@sanity/production-preview" causing part conflict error
This error occurs because your sanity.json configuration has incorrectly combined two separate parts into one entry. The error message is confusing (showing the same plugin twice) because the parts system is detecting a conflict in how you've declared the schema part.
The Problem
In your sanity.json, you likely have something like:
"parts": [
{
"name": "part:@sanity/base/schema",
"implements": "part:@sanity/production-preview/resolve-production-url",
"path": "./resolve-production-url.js"
}
]This is combining your schema declaration with the production preview implementation, which causes the resolver to fail. The name property declares a part, while implements provides an implementation for a different part - they shouldn't be in the same object.
The Solution
As explained in this answer about fixing parts in sanity.json, you need to separate these into distinct part entries. Your sanity.json should look like this:
"parts": [
{
"name": "part:@sanity/base/schema",
"path": "./schemas/schema.js"
},
{
"implements": "part:@sanity/production-preview/resolve-production-url",
"path": "./resolve-production-url.js"
}
]Make sure the path to your schema file is correct (it should point to your actual schema file, like ./schemas/schema.js or wherever you've defined your schema).
If you also have a desk structure, add it as a separate part:
"parts": [
{
"name": "part:@sanity/base/schema",
"path": "./schemas/schema.js"
},
{
"name": "part:@sanity/desk-tool/structure",
"path": "./deskStructure.js"
},
{
"implements": "part:@sanity/production-preview/resolve-production-url",
"path": "./resolve-production-url.js"
}
]Important Context
This is a Sanity Studio v2 issue - the "parts" system was completely removed in Studio v3. If you're starting a new project or can upgrade, I'd strongly recommend moving to Studio v3, which has a much simpler plugin system and avoids these types of configuration conflicts entirely.
Additionally, the sanity-plugin-transifex plugin appears to be designed for Studio v2. Before investing time in fixing this, check if the plugin has been updated for Studio v3 compatibility, or if there's an alternative translation solution that works with the current version of Sanity.
Show original thread5 replies
Sanity – Build the way you think, not the way your CMS thinks
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.