Forum Discussion
Bundling and "externals"
- Jul 14, 2017
You don't need to do this. What you're looking at is a project created an older version of the SharePoint Framework, where more packages have been listed as external. In the latest version it's not required anymore which is why you're not seeing them anymore.
Thanks, yeah, I've played with that and got it to work fine. But given the fine details (limited support for Private CDN, and Public CDN being...well, *public*), that solution is a non-starter for my customer -- they're much more comfortable with their assets continuing to be contained directly within their own SP sites. A dedicated site collection, site and document libraries are serving that function well at the moment. If the customer comes back to me at a later date worried about performance, I can have the CDN talk with them again.
My question is not about where the assets should be stored -- it's about which ones I should instruct the tool chain to treat as external to the project so I don't end up bundling the same code into multiple web parts which will be running on the same page. I'd like to lighten the web parts as much as possible to improve page-load performance on the intranet.
- Joseph AckermanJul 19, 2017Iron Contributor
Interesting that you would say that because that's not what I remember from his demo, and a subsequent Webinar on JS security from Rencore a few weeks ago made a point of saying that using a CDN was a trade-off to get better performance at the expense of the asset's security.
Can you point me to the "spot" in the video where Vesa says this? Thanks.
- Jul 20, 2017
I don't know about the exact bit you're referring to, but what Vesa said, makes sense if you're thinking about using a public CDN. Imagine: you're loading a script from a location that you have no control over. If that script gets hacked, and given that it's running without any restrictions on your intranet pages, it could be used to gain access to your confidential data. This risk is not specific to CDNs: any location that's not properly secured and doesn't have its governance in place poses the same risks.
It's worth keeping in mind that using a CDN doesn't guarantee a better performance. If your organization has one office or is located in one region, you could get better performance from a hosting location optimized for serving static assets than from a CDN. CDN offers you the most benefits, when your users are spread all over the world.
- Dean_GrossJul 20, 2017Silver Contributor
See the FAQ in the announcement at https://dev.office.com/blogs/general-availability-of-office-365-cdn
- Joseph AckermanJul 20, 2017Iron Contributor
Thanks, guys. Very helpful information. Should help clarify things for the client! :)