Sp-dev-fx-webparts: component id {0} exists in solution {1} already

[Brentless]

Category

• [X] Question
• [ ] Bug
• [] Enhancement

Authors

@wobba

Expected or Desired Behavior

I have a version of the Modern Script Editor web part (basically version 1 when it first came out), and I would like to load a second version of it. I have tried updating the v1 model, but it hasn't worked, and I would rather load a second instance and start manually switching over the previous work. Expectation is to have two script editor web parts in the same site with different names.

Observed Behavior

Basically what I have done is completely switched out the GUIDs in the manifest.json and the package-solution.json for completely new values, and given it a different name in the package-solution.json. When I load it up, I get an error in the "Apps for SharePoint" page that says:

"component id {0} exists in solution {1} already"

Is there something else that needs to be different in order for SharePoint to not view the web parts as conflicts?

Steps to Reproduce

Listed above

[wobba]

@Brentless you can not have two versions of the same spfx web part, and it should upgrade just fine, as the behaviour is pretty identical - only improvements. If you want two versions you need to change the component id when building, so that it’s not seen as the same web part. And seems you have done this, but might have missed a guid somewhere. Check in package.json and manifest for the wp.

Basically when you deploy an SPFx part, it will always serve the latest .js file, regardless of what version you installed.

If you use the site collection app catalog, two site collections can have different versions.

[VelinGeorgiev]

If you use the site collection app catalog, sometimes SharePoint does not clean /Lists/ComponentManifests/ properly. There might be id there belonging to different or old uninstalled package and then you have conflict.

Some findings here:
https://blog.velingeorgiev.com/sharepoint-spfx-component-id-0-exists-solution-1-already-error

[Brentless]

ok, i've found part of my issue here. i wasnt doing a gulp clean in my process, so it had some "ghost" entries that were making there way into the final build.

I've got another one, where I'll open another post, but now my web part works fine in regular site collections, but not modern pages in Communication sites.

[KoenZomers]

Thanks for reporting this back @Brentless. That saved me from spending a whole lot of time figuring this out myself :) Ran into the same thing.

[NarenderSingh]

Check Point No. B
https://github.com/NarenderSingh/spfx-commands