Jul 26 2016 09:22 AM - edited Jul 26 2016 09:28 AM
Both the Document Library and Site Contents New Experience load requireJS first.
Can we count on it being available by default for all future developments or can there be scenarios where it will not be available in SharePoint Fx pages?
We now include requireJS in our own (single file distribution) Framework, if its available by default I can take it out the built/package (eventually)
Same question for React
tnx
Jul 28 2016 12:41 AM
We probably have to wait till Ignite to get an official answer. My bet would be, don't count on it, as they might change to other frameworks if they feel the need to do so.
Jul 28 2016 05:10 AM
SolutionDon't count on require.js for SPFx. Require.js is in most cases outdated in favor of System.js, which is what you should look into.
Also the SPFx is based on Webpack; so the focus is more on bundling assets rather than loading them on demand in this first release.
Jul 28 2016 12:17 PM
Cool
Bundling assets; finally a technology I already master
copy /b file1.js file2.js fileout.js
Now how can we close a question like we can on SharePoint.StackExchange?
Aug 01 2016 11:42 PM
Aug 02 2016 02:31 AM
Yes, that's exactly how it will be if multiple vendors bundles jQuery. But, exactly how this will work and solved will be annonced once SPFx is out in public.