You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know the readme said only [Office 365 tenant] but maybe you can help me convert this to SP2016 On-prem.
I looked at Vanilla SP2016 package.json and all the "@microsoft/* had version "~1.1.0" and your project had "^1.3.4".
So, on my package.json I changed all the 1.3.4 to 1.1.0 and ran npm install.
When running the workbench on my site, adding the web part shows error pertaining to version "1.3.4"
see below.
Is there any hope for a clean process to convert samples to 2016 on-prem? :-)
Thank you in advance
`***ERROR MESSAGE:
***Failed to load component "48e2d130-7eb7-4ee9-aa23-5ddbdfd175b2" (ListFormWebPart).
Original error: ***Manifest not found for component id "7263c7d0-1d6a-45ec-8d85-d4d1d234171b" and version "1.3.4".
I know the readme said only [Office 365 tenant] but maybe you can help me convert this to SP2016 On-prem.
I looked at Vanilla SP2016 package.json and all the "@microsoft/* had version "~1.1.0" and your project had "^1.3.4".
So, on my package.json I changed all the 1.3.4 to 1.1.0 and ran npm install.
When running the workbench on my site, adding the web part shows error pertaining to version "1.3.4"
see below.
Is there any hope for a clean process to convert samples to 2016 on-prem? :-)
Thank you in advance
`***ERROR MESSAGE:
***Failed to load component "48e2d130-7eb7-4ee9-aa23-5ddbdfd175b2" (ListFormWebPart).
Original error: ***Manifest not found for component id "7263c7d0-1d6a-45ec-8d85-d4d1d234171b" and version "1.3.4".
***CALLSTACK:
Error: ***Failed to load component "48e2d130-7eb7-4ee9-aa23-5ddbdfd175b2" (ListFormWebPart).
Original error: ***Manifest not found for component id "7263c7d0-1d6a-45ec-8d85-d4d1d234171b" and version "1.3.4".
at http://sp16.gal.home/_layouts/15/next/spfx/sp-webpart-workbench-assembly_en-us.js?version=1:675:105711 at anonymous `
The text was updated successfully, but these errors were encountered: