Forum Discussion
Joseph Ackerman
Jul 06, 2017Iron Contributor
Bundling and "externals"
My current project uses jQuery and sp-pnp-js, and I have moved these to a document library in a "cdn" site collection in my tenant (it's not a *real* CDN, I just call it that -- it really is just a d...
- 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.
Dean_Gross
Jul 08, 2017Silver Contributor
Sorry, I don't know the answer to your specific question, but you may be interested in using a real CDN that MS recently announced support for, see https://dev.office.com/blogs/general-availability-of-office-365-cdn for the details
Joseph Ackerman
Jul 10, 2017Iron Contributor
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.
- Dean_GrossJul 10, 2017Silver Contributor"Public" is a poorly choosen word, all that it means is that anyone who has access to the tenant will have access to the resource. If you are not already logged into the tenant then you cannot get to the item in the "public CDN". VesaJuvonen explained this in his demo.
- 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.
- Dean_GrossJul 20, 2017Silver Contributor
See the FAQ in the announcement at https://dev.office.com/blogs/general-availability-of-office-365-cdn