react-script-editor - Component ID exist in another solution

[IfEyeOnlyKnew]

Disclaimer

Yes

Sample

react-script-editor

Contributor(s)

@wobba @salascz @felixbohnacker

What happened?

We have the classic version of the script editor web part, but installing the modern script editor the app packaage error message shows up: <
Component ID {3A328F0A-99C4-4B28-95AB-FE0847F657A3} exists in solution 1425175f-3ed8-44d2-8fc4-dd1497191294 already.

I did run through the instructions to Deploy. Can I have both classic version script editor and modern? I wondering can I change the Component ID on the Modern version somewhere - #620?

Thanks

Steps to reproduce

Just installed in the app catalog.

Expected behavior

Both versions work.

Target SharePoint environment

SharePoint Online

Developer environment

None

Browsers

• Internet Explorer
• Microsoft Edge
• Google Chrome
• FireFox
• Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

What version of Node.js is currently installed on your workstation?

v20.12.1

What version of Node.js is required by the sample?

v20.12.1

Paste the results of SPFx doctor

Don't have anything to paste

Additional environment details

Thanks for looking into this.

[wobba]

Seems you may have installed the package already as 1425175f-3ed8-44d2-8fc4-dd1497191294 is the solution id of the modern script editor web part (a solution you should not use btw :) Maybe someone name the sppkg something else?

https://github.com/pnp/sp-dev-fx-webparts/blob/main/samples/react-script-editor/config/package-solution.json#L5

[IfEyeOnlyKnew]

So, I have modern script editor installed on our Development, but not the older version of script editor web part (classic). It is the opposite in our Prod tenant, but the same issue pops up for both when installing the one that is not installed.

Thanks for your response. Do you have some insights for your comment?

"...solution id of the modern script editor web part (a solution you should not use btw :)"

I am not familiar with creating a new Guid for package-solution.json. Do you have some advice?

[wobba]

What do you mean old/new? Classic has a built-in webpart, nothing to do with SPFx. The error points to an existing .sppkg being installed in your app catalog. My assumption would be under a different filename.

[IfEyeOnlyKnew]

Does this make sense that we have a classic version?

[wobba]

That's a SPFx modern web part used on a classic page 🙂 You can use the same web part on modern pages. No need to readd the sppkg unless you have changed some config building it (https://github.com/pnp/sp-dev-fx-webparts/blob/main/samples/react-script-editor/README.md#deploy-to-non-script-sites--modern-team-sites)

You also might want to read my blog post https://www.techmikael.com/2024/03/allowing-arbitrary-custom-scripting-in.html

[IfEyeOnlyKnew]

Thank you for your comments, Mikael! I appreciate the feedback. Closing the case.

Thank you for the links as well.