Forum Discussion
SharePoint framework react-script editor web part error
- Sep 04, 2017
You're trying to load artefacts from https://publiccdn.sharepointonline.com/techmikael.sharepoint.com/ - AFAIK that is the SharePoint tenant of Mikael Svensson, and not you :-)
Modify the config/config.json to point to YOUR location where you have your Office UI Fabric React components
Hi Mikael, can this web part be run on SharePoint 2019 on-prem? By on-prem in this case there are no internet connection.
I get the webpart running on my dev laptop in workbench. But when building a package an deploying it to the on-prem environment. I get a lot of errors on the webpart. Failed to load manifest and so on...
I'm just starting experimenting with spfx, and trying to implement your webpart in my companys dev environment.
The error output is:
SPLoaderError.loadComponentError]:
***Failed to load component "3a328f0a-99c4-4b28-95ab-fe0847f657a3" (ScriptEditorWebPart).
Original error: ***Manifest not found for component id "974a7777-0990-4136-8fa6-95d80114c2e0" and version "1.5.1".
***INNERERROR:
***Manifest not found for component id "974a7777-0990-4136-8fa6-95d80114c2e0" and version "1.5.1".
***CALLSTACK:
Error
at t._generateErrorStackForIE (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:356:16078)
at t (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:356:15614)
at t (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:22166)
at e.buildErrorWithVerboseLog (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:14402)
at e.buildLoadComponentError (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:10817)
at Anonymous function (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:62074)
at A (http://sharepointsite.x.xxx/_layouts/15/next/spclient/10.sp-pages-search.js:8:1743)
at k (http://sharepointsite.x.xxx/_layouts/15/next/spclient/10.sp-pages-search.js:8:1831)
at Anonymous function (http://sharepointsite.x.xxx/_layouts/15/next/spclient/10.sp-pages-search.js:8:5649)
at h (http://sharepointsite.x.xxx/_layouts/15/next/spclient/10.sp-pages-search.js:8:344)
- Mikael SvensonJan 29, 2019Iron Contributor
Hi,
You probably need to downgrade Pernille-Eskebo npm packages to ~1.1.0 and possibly edit tsconfig.json and .yo-rc.json. If you create a dummy SPFx 2016 part - and copy the configs you should be able to get it working.
Guess I could do the work myself - but don't have any on-prem environments to test on :) If you create a PR which updates to SPFx v1.7.1 and changes lib compat to online as well I'll merge it.
- Hans Kristian KristoffersenMar 15, 2019Copper Contributor
Hi again Mikael, just wanted to tell you I got your webpart working in SharePoint 2019 on-prem (offline)
Seems the biggest issue is that when you create a project with the React Framework, it uses version 16.x.x of React which 2019 does not support. Downgrading to a version of the 15 release did the trick.
- nehasha108Apr 02, 2019Copper Contributor
I have the same issue and verified the version of React in my config file is 15.6.6 but still the exact same issue.
Failed to load component "3a328f0a-99c4-4b28-95ab-fe0847f657a3" (ScriptEditorWebPart).
Original error: ***Manifest not found for component id "974a7777-0990-4136-8fa6-95d80114c2e0" and version "1.5.1"Here is my package.json file:
- Jason KatzFeb 06, 2019Copper ContributorI too received the error mentioned above. Sorry to bother, I'm new to this - so any help would be appreciated!
- Mikael SvensonFeb 06, 2019Iron Contributor..and the part is made for online. Onprem requires an effort.