xmpp.chapril.org-conversejs/src/start.frag

/** Converse.js
 *
 *  An XMPP chat client that runs in the browser.
 *
 *  Version: 3.3.4
 */

/* jshint ignore:start */
(function (root, factory) {
    root.converse = factory();
}(this, function () {
    //almond, and your modules will be inlined here
/* jshint ignore:end */
Rework the way builds are created. Builds are now themselves UMD modules, so they could be `require`'d like any other AMD module or they can still be used as old ES5 modules with globals. Additionally the build is now closured, so that the almond API doesn't pollute the global context with `define` or `require`. This does however mean that `require` can no longer be used outside of the build (unless requirej.s is included directly. 2017-02-27 08:42:17 +01:00			`/** Converse.js`
			`*`
			`* An XMPP chat client that runs in the browser.`
			`*`
Release 3.3.4 2018-03-05 14:43:53 +01:00			`* Version: 3.3.4`
Rework the way builds are created. Builds are now themselves UMD modules, so they could be `require`'d like any other AMD module or they can still be used as old ES5 modules with globals. Additionally the build is now closured, so that the almond API doesn't pollute the global context with `define` or `require`. This does however mean that `require` can no longer be used outside of the build (unless requirej.s is included directly. 2017-02-27 08:42:17 +01:00			`*/`

			`/* jshint ignore:start */`
			`(function (root, factory) {`
Don't wrap the build in an anonymous `define`. This cause the error "Mismatched anonymous define" when loading the bundle in Plone. The original reason for adding `start.frag` was to wrap the bundle in a closure to not pollute the global namespace (e.g. overriding global `define` and `require` with Almond`s versions) and secondarily to allow people to load the bundle via require.js. The second usecase should now probably be done via a shim in the require.js config. 2018-03-25 11:33:01 +02:00			`root.converse = factory();`
Rework the way builds are created. Builds are now themselves UMD modules, so they could be `require`'d like any other AMD module or they can still be used as old ES5 modules with globals. Additionally the build is now closured, so that the almond API doesn't pollute the global context with `define` or `require`. This does however mean that `require` can no longer be used outside of the build (unless requirej.s is included directly. 2017-02-27 08:42:17 +01:00			`}(this, function () {`
			`//almond, and your modules will be inlined here`
			`/* jshint ignore:end */`