"Content Embed" vs "Script Editor" in the new modern pages

[Brent Ellis]

So I have done a lot of simple Script Editor Web Parts in my day

Is the Script Editor Web Part coming back in modern pages?

Is the purpose of the Content Embed web part in the modern pages to replace that?   

Or am I forced to use the SPFx whenever that gets incorporated?

[#2]

Good question. I've been playing with the new method and it looks to be more limited than the one it replaces. Also looks like it uses iframes which I thought was last years tech.

[#3]

IMHO you will be forced to use the new SPFx...I also expect a SPFx WebPart replacement for the script editor WebPart and I also think it's not too bad because you will be able to overcome limitations of the script editor webpart such as the lacks of add configuration parameters...something you will get with SPFx WebParts

[#4]

my biggest argument (while yes i will eventually learn SPFx), is how SIMPLE the script editor web part it, i think it is highly valuable as is, and forcing SPFx will complicate some very simple JS+HTML workloads. Just another set of massive reworks required for us to "migrate" into modern....

[#5]

I know that this will imply a massive rework :-(...Indeed this morning I had a very interesting talk with an ISV that has an Intranet product for SPO and they are currently working on replacing all the script editor WebParts they provision (using remote provisioning) when installing their product by SPFx WebParts

[#6]

For anyone interested, starting a lobby to bring back SEWP in modern sharepoint.

https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/17290130-bring-ba...
______________

The Script Editor Web Part has been replaced by the Content Editor (which does a very limited iframe) and the new SPFX stuff. I am not a developer, but knowledgeable in HTML, Javascript, CSS. The SEWP met some very complex use cases (targeted for replacement by SPFX), but also some very simple use cases.

Example: Insert a formatted single HTML button, something that is big, draws attention, and encourages the user to click it to start an action.

What might be just 2 lines of code, has now turned into (what looks like) hundreds of files of deployment, installing all kinds of tools that I have never heard of or know what they are actually doing in the background.

I am finding SPFX to be specifically geared toward professional developers and limiting "citizen" developers from adding just simple things to SharePoint pages. I am trying to learn it, but there are so many things above my head at this point, and my role is not to be a full-time developer.

This is to lobby to bring back the Script Editor Web Part to meet simple use cases

[#7]

Shout out to @Mikael Svenson, after some muddling through some gulping and serving, and other things I dont know what I'm doing, I have a Script Editor Web Part in modern sharepoint!

This is going to save all kinds of time!

I say boo to all the legit developers that are saying this shouldnt be a thing.  At least for my organization, this is a huge value-add and will help us start transitioning into modern sharepoint alot faster.

I've tested many of my more complicated SEWP and all working perfecting in Mikael's web part!

Couple links of note:

https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor

http://ericoverfield.com/script-editor-webpart-sewp-now-available-for-the-sharepoint-framework-spfx-...

[#8]

Happy you could use it :) Next add would be to point to a file, but I'll wait until sp-filepicker is available as a component.

We're using it at a customer to add a big red button, navigating to a policy page :)

[#9]

Hello Everyone,

I would also recommend you to try the below one. This is very good and lot of options to include custom script/css/content

https://github.com/jcoleman-pcprofessional/True-Script-Editor

Thanks & Regards,

Bhanu