Forum Discussion
SharePoint SPX development webpart
- Mar 12, 2019
Hi Vishwanatha,
Thanks for your reply, seems to be it is working now. But I haven't done any specific changes, so I cannot post the answer/ findings.
Only thing that I can think of is save every changes before run the gulp serve.
Thanks all.
I think public CDN is enabled on your tenant, could be the reason why your are facing this caching stuff.
Please check the reference of your assets is it coming form a public CDN or not, if it is a Public CDN and it take sometime to update the assets over there post your changes.
Refer below for more idea on public CDN
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn
HI Ujwaln,
Thanks for your reply, could you you please explain to me why I need to worry about the tenancy setting as I m trying to running on the local host.
Thanks.
- Vishwanatha NayakMar 12, 2019Brass Contributor
Hi Nipuna,
What happens when you browse https://localhost:4321, does it get served or do you see any issues:
1) Check if you have added dev cert using gulp dev cert
2) If the above site gives protocol error you need add a environment variable as mentioned here https://github.com/SharePoint/sp-dev-fx-webparts/issues/357
- nipWMar 12, 2019Brass Contributor
Hi Vishwanatha,
Thanks for your reply, seems to be it is working now. But I haven't done any specific changes, so I cannot post the answer/ findings.
Only thing that I can think of is save every changes before run the gulp serve.
Thanks all.