jsviews seems incompatible with browserify #254

badiezadegan · 2014-04-20T09:54:33Z

How can jsviews get compatible with browserify?

BorisMoore · 2014-04-21T22:44:08Z

Do you know what is needed to make it compatible?

badiezadegan · 2014-04-23T06:28:54Z

I don't know exactly. But it looks jsviews is prepared for require.js modules but browserify is for node.js modules. It seems one should write a shim for jsviews to get it work with browserify.

gbouthenot · 2014-04-23T08:31:19Z

According to http://requirejs.org/ :
RequireJS is a JavaScript file and module loader. It is optimized for in-browser use, but it can be used in other JavaScript environments, like Rhino and Node.
Here is the documentation for node:
http://requirejs.org/docs/node.html

I also found this text that seems very useful:
http://esa-matti.suuronen.org/blog/2013/03/22/journey-from-requirejs-to-browserify/

BorisMoore · 2014-04-23T23:52:09Z

OK. I plan to add support for bower, nodejs, AMD/require, Nuget, webjars, composer, typescript... for V1 - and I will try to make this (browserify) work too.
Also, add to CDN https://cdnjs.com/.
Meantime there is already a node package wrapper here https://www.npmjs.org/package/node-jsrender maintained by @coolbloke1324.

badiezadegan · 2014-04-24T01:54:06Z

Thanks a lot.

BorisMoore · 2014-04-24T01:55:40Z

np - but I'll reopen as a reminder to myself to do this on reaching V1.0. :)

BREAKING CHANGES AND IMPROVEMENTS - The global namespace when JsRender is loaded without jQuery is now window.jsrender. (Previously it was window.jsviews). So when using JsRender without jQuery, you can write: var $ = jsrender; - and use the $ var it in the same way you would use the global $ when JsRender is loaded with jQuery: e.g. $.templates(...) or $.views.helpers(...) etc. - AMD support has been improved and simplified. All AMD modules, including JsRender, with or without jQuery, now return the jQuery object (if loaded) or the analogous JsViews object. - Node.js support and integration has been improved - along with improved CommonJS support, and Browserify integration. The file system APIs now use the syntax tmpl="./file/path.html". The Node.js version of jsrender.js is available as a separate file (available at //jsviews.com/download/jsrender-node.js). The Node.js version of JsRender provides the complete set of JsRender APIs and features, together with integration with NodeJS view-engines such as Express and Hapi, APIs for loading templates from the file system, etc. The file system APIs now use the syntax tmpl="./file/path.html". It also includes a built-in Browserify transform (see "Browserify Support: below). (Note: JsRender and JsViews will soon be published to NPM). - The behavior when loading multiple instances of JsRender or JsViews files has been changed: When loading a new instance, the previous instance $.views, $.templates, etc. is no longer overwritten. So a component using JsRender or JsViews will not, when loaded, cause another already loaded component also using JsViews/JsRender to fail (except for collisions arising in the unlikely case where both happen to use the same template/converter/helper name). As part of this modified behavior, the noConflict support for JsRender had been removed. NEW FEATURES - observeAll() for cyclic objects is now supported for the vast majority of cases. See BorisMoore/jsviews#304 - Improved support for data-linking to data- attributes: <elem data-link="data-foo{:expr}" ...>. After data-linking, the value of the data-foo attribute will be expr.toString(), but $.data(element, "foo") and $(element).data("foo") will actually return the value of expr, even if of type object. See BorisMoore/jsviews#306 - Browserify Support: JsRender on Node.js provides a built-in Browserify transform - jsrender.tmplify, for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var $jsr = require('jsrender'); browserify(...) ... .transform($jsr.tmplify) ... See also http://www.jsviews.com/test/unit-tests-browserify.html - Initial work for deployment to Bower and NPM. See BorisMoore/jsviews#254 BorisMoore/jsrender#225 Bug Fixes: - BorisMoore/jsrender#263 BorisMoore/jsrender#264 Caching of template on script elements. (Unit tests added) - BorisMoore/jsviews#304 ObserveAll on cyclic objects - BorisMoore/jsviews#306 'data-xxxx' attribute using data-link - BorisMoore/jsviews#307 BorisMoore/jsviews#312

BREAKING CHANGES AND IMPROVEMENTS - The global namespace when JsRender is loaded without jQuery is now window.jsrender. (Previously it was window.jsviews). So when using JsRender without jQuery, you can write: var $ = jsrender; - and use the $ var it in the same way you would use the global $ when JsRender is loaded with jQuery: e.g. $.templates(...) or $.views.helpers(...) etc. - AMD support has been improved and simplified. All AMD modules, including JsRender, with or without jQuery, now return the jQuery object (if loaded) or the analogous JsViews object. - Node.js support and integration has been improved - along with improved CommonJS support, and Browserify integration. The file system APIs now use the syntax tmpl="./file/path.html". The Node.js version of jsrender.js is available as a separate file (available at //jsviews.com/download/jsrender-node.js). The Node.js version of JsRender provides the complete set of JsRender APIs and features, together with integration with NodeJS view-engines such as Express and Hapi, APIs for loading templates from the file system, etc. The file system APIs now use the syntax tmpl="./file/path.html". It also includes a built-in Browserify transform (see "Browserify Support: below). (Note: JsRender and JsViews will soon be published to NPM). - The behavior when loading multiple instances of JsRender or JsViews files has been changed: When loading a new instance, the previous instance $.views, $.templates, etc. is no longer overwritten. So a component using JsRender or JsViews will not, when loaded, cause another already loaded component also using JsViews/JsRender to fail (except for collisions arising in the unlikely case where both happen to use the same template/converter/helper name). As part of this modified behavior, the noConflict support for JsRender had been removed. NEW FEATURES - observeAll() for cyclic objects is now supported for the vast majority of cases. See #304 - Improved support for data-linking to data- attributes: <elem data-link="data-foo{:expr}" ...>. After data-linking, the value of the data-foo attribute will be expr.toString(), but $.data(element, "foo") and $(element).data("foo") will actually return the value of expr, even if of type object. See #306 - Browserify Support: JsRender on Node.js provides a built-in Browserify transform - jsrender.tmplify, for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var $jsr = require('jsrender'); browserify(...) ... .transform($jsr.tmplify) ... See also http://www.jsviews.com/test/unit-tests-browserify.html - Initial work for deployment to Bower and NPM. See #254 BorisMoore/jsrender#225 Bug Fixes: - BorisMoore/jsrender#263 BorisMoore/jsrender#264 Caching of template on script elements. (Unit tests added) - #304 ObserveAll on cyclic objects - #306 'data-xxxx' attribute using data-link - #307 #312

BREAKING CHANGES AND IMPROVEMENTS - The global namespace when JsRender is loaded without jQuery is now window.jsrender. (Previously it was window.jsviews). So when using JsRender without jQuery, you can write: var $ = jsrender; - and use the $ var it in the same way you would use the global $ when JsRender is loaded with jQuery: e.g. $.templates(...) or $.views.helpers(...) etc. - AMD support has been improved and simplified. All AMD modules, including JsRender, with or without jQuery, now return the jQuery object (if loaded) or the analogous JsViews object. - Node.js support and integration has been improved - along with improved CommonJS support, and Browserify integration. The file system APIs now use the syntax tmpl="./file/path.html". The Node.js version of jsrender.js is available as a separate file (available at //jsviews.com/download/jsrender-node.js). The Node.js version of JsRender provides the complete set of JsRender APIs and features, together with integration with NodeJS view-engines such as Express and Hapi, APIs for loading templates from the file system, etc. The file system APIs now use the syntax tmpl="./file/path.html". It also includes a built-in Browserify transform (see "Browserify Support: below). (Note: JsRender and JsViews will soon be published to NPM). - The behavior when loading multiple instances of JsRender or JsViews files has been changed: When loading a new instance, the previous instance $.views, $.templates, etc. is no longer overwritten. So a component using JsRender or JsViews will not, when loaded, cause another already loaded component also using JsViews/JsRender to fail (except for collisions arising in the unlikely case where both happen to use the same template/converter/helper name). As part of this modified behavior, the noConflict support for JsRender had been removed. NEW FEATURES - Browserify Support: JsRender on Node.js provides a built-in Browserify transform - jsrender.tmplify, for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var $jsr = require('jsrender'); browserify(...) ... .transform($jsr.tmplify) ... See also http://www.jsviews.com/test/unit-tests-browserify.html - Initial work for deployment to Bower and NPM. See BorisMoore/jsviews#254 #225 Bug Fixes: - #263 #264 Caching of template on script elements. (Unit tests added)

BREAKING CHANGES AND IMPROVEMENTS - The global namespace when JsRender is loaded without jQuery is now window.jsrender. (Previously it was window.jsviews). So when using JsRender without jQuery, you can write: var $ = jsrender; - and use the $ var it in the same way you would use the global $ when JsRender is loaded with jQuery: e.g. $.templates(...) or $.views.helpers(...) etc. - AMD support has been improved and simplified. All AMD modules, including JsRender, with or without jQuery, now return the jQuery object (if loaded) or the analogous JsViews object. - Node.js support and integration has been improved - along with improved CommonJS support, and Browserify integration. The file system APIs now use the syntax tmpl="./file/path.html". The Node.js version of jsrender.js is available as a separate file (available at //jsviews.com/download/jsrender-node.js). The Node.js version of JsRender provides the complete set of JsRender APIs and features, together with integration with NodeJS view-engines such as Express and Hapi, APIs for loading templates from the file system, etc. The file system APIs now use the syntax tmpl="./file/path.html". It also includes a built-in Browserify transform (see "Browserify Support: below). (Note: JsRender and JsViews will soon be published to NPM). - The behavior when loading multiple instances of JsRender or JsViews files has been changed: When loading a new instance, the previous instance $.views, $.templates, etc. is no longer overwritten. So a component using JsRender or JsViews will not, when loaded, cause another already loaded component also using JsViews/JsRender to fail (except for collisions arising in the unlikely case where both happen to use the same template/converter/helper name). As part of this modified behavior, the noConflict support for JsRender had been removed. NEW FEATURES - observeAll() for cyclic objects is now supported for the vast majority of cases. See BorisMoore/jsviews#304 - Improved support for data-linking to data- attributes: <elem data-link="data-foo{:expr}" ...>. After data-linking, the value of the data-foo attribute will be expr.toString(), but $.data(element, "foo") and $(element).data("foo") will actually return the value of expr, even if of type object. See BorisMoore/jsviews#306 - Browserify Support: JsRender on Node.js provides a built-in Browserify transform - jsrender.tmplify, for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var $jsr = require('jsrender'); browserify(...) ... .transform($jsr.tmplify) ... See also http://www.jsviews.com/test/unit-tests-browserify.html - Initial work for deployment to Bower and NPM. See BorisMoore/jsviews#254 BorisMoore/jsrender#225 Bug Fixes: - BorisMoore/jsrender#263 BorisMoore/jsrender#264 Caching of template on script elements. (Unit tests added) - BorisMoore/jsviews#304 ObserveAll on cyclic objects - BorisMoore/jsviews#306 'data-xxxx' attribute using data-link - BorisMoore/jsviews#307 BorisMoore/jsviews#312

BREAKING CHANGES AND IMPROVEMENTS - The global namespace when JsRender is loaded without jQuery is now window.jsrender. (Previously it was window.jsviews). So when using JsRender without jQuery, you can write: var $ = jsrender; - and use the $ var it in the same way you would use the global $ when JsRender is loaded with jQuery: e.g. $.templates(...) or $.views.helpers(...) etc. - AMD support has been improved and simplified. All AMD modules, including JsRender, with or without jQuery, now return the jQuery object (if loaded) or the analogous JsViews object. - Node.js support and integration has been improved - along with improved CommonJS support, and Browserify integration. The file system APIs now use the syntax tmpl="./file/path.html". The Node.js version of jsrender.js is available as a separate file (available at //jsviews.com/download/jsrender-node.js). The Node.js version of JsRender provides the complete set of JsRender APIs and features, together with integration with NodeJS view-engines such as Express and Hapi, APIs for loading templates from the file system, etc. The file system APIs now use the syntax tmpl="./file/path.html". It also includes a built-in Browserify transform (see "Browserify Support: below). (Note: JsRender and JsViews will soon be published to NPM). - The behavior when loading multiple instances of JsRender or JsViews files has been changed: When loading a new instance, the previous instance $.views, $.templates, etc. is no longer overwritten. So a component using JsRender or JsViews will not, when loaded, cause another already loaded component also using JsViews/JsRender to fail (except for collisions arising in the unlikely case where both happen to use the same template/converter/helper name). As part of this modified behavior, the noConflict support for JsRender had been removed. NEW FEATURES - observeAll() for cyclic objects is now supported for the vast majority of cases. See #304 - Improved support for data-linking to data- attributes: <elem data-link="data-foo{:expr}" ...>. After data-linking, the value of the data-foo attribute will be expr.toString(), but $.data(element, "foo") and $(element).data("foo") will actually return the value of expr, even if of type object. See #306 - Browserify Support: JsRender on Node.js provides a built-in Browserify transform - jsrender.tmplify, for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var $jsr = require('jsrender'); browserify(...) ... .transform($jsr.tmplify) ... See also http://www.jsviews.com/test/unit-tests-browserify.html - Initial work for deployment to Bower and NPM. See #254 BorisMoore/jsrender#225 Bug Fixes: - BorisMoore/jsrender#263 BorisMoore/jsrender#264 Caching of template on script elements. (Unit tests added) - #304 ObserveAll on cyclic objects - #306 'data-xxxx' attribute using data-link - #307 #312

BREAKING CHANGES AND IMPROVEMENTS - The global namespace when JsRender is loaded without jQuery is now window.jsrender. (Previously it was window.jsviews). So when using JsRender without jQuery, you can write: var $ = jsrender; - and use the $ var it in the same way you would use the global $ when JsRender is loaded with jQuery: e.g. $.templates(...) or $.views.helpers(...) etc. - AMD support has been improved and simplified. All AMD modules, including JsRender, with or without jQuery, now return the jQuery object (if loaded) or the analogous JsViews object. - Node.js support and integration has been improved - along with improved CommonJS support, and Browserify integration. The file system APIs now use the syntax tmpl="./file/path.html". The Node.js version of jsrender.js is available as a separate file (available at //jsviews.com/download/jsrender-node.js). The Node.js version of JsRender provides the complete set of JsRender APIs and features, together with integration with NodeJS view-engines such as Express and Hapi, APIs for loading templates from the file system, etc. The file system APIs now use the syntax tmpl="./file/path.html". It also includes a built-in Browserify transform (see "Browserify Support: below). (Note: JsRender and JsViews will soon be published to NPM). - The behavior when loading multiple instances of JsRender or JsViews files has been changed: When loading a new instance, the previous instance $.views, $.templates, etc. is no longer overwritten. So a component using JsRender or JsViews will not, when loaded, cause another already loaded component also using JsViews/JsRender to fail (except for collisions arising in the unlikely case where both happen to use the same template/converter/helper name). As part of this modified behavior, the noConflict support for JsRender had been removed. NEW FEATURES - Browserify Support: JsRender on Node.js provides a built-in Browserify transform - jsrender.tmplify, for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var $jsr = require('jsrender'); browserify(...) ... .transform($jsr.tmplify) ... See also http://www.jsviews.com/test/unit-tests-browserify.html - Initial work for deployment to Bower and NPM. See BorisMoore/jsviews#254 #225 Bug Fixes: - #263 #264 Caching of template on script elements. (Unit tests added)

BREAKING CHANGES AND IMPROVEMENTS - The global namespace when JsRender is loaded without jQuery is now window.jsrender. (Previously it was window.jsviews). So when using JsRender without jQuery, you can write: var $ = jsrender; - and use the $ var it in the same way you would use the global $ when JsRender is loaded with jQuery: e.g. $.templates(...) or $.views.helpers(...) etc. - AMD support has been improved and simplified. All AMD modules, including JsRender, with or without jQuery, now return the jQuery object (if loaded) or the analogous JsViews object. - Node.js support and integration has been improved - along with improved CommonJS support, and Browserify integration. The file system APIs now use the syntax tmpl="./file/path.html". The Node.js version of jsrender.js is available as a separate file (available at //jsviews.com/download/jsrender-node.js). The Node.js version of JsRender provides the complete set of JsRender APIs and features, together with integration with NodeJS view-engines such as Express and Hapi, APIs for loading templates from the file system, etc. The file system APIs now use the syntax tmpl="./file/path.html". It also includes a built-in Browserify transform (see "Browserify Support: below). (Note: JsRender and JsViews will soon be published to NPM). - The behavior when loading multiple instances of JsRender or JsViews files has been changed: When loading a new instance, the previous instance $.views, $.templates, etc. is no longer overwritten. So a component using JsRender or JsViews will not, when loaded, cause another already loaded component also using JsViews/JsRender to fail (except for collisions arising in the unlikely case where both happen to use the same template/converter/helper name). As part of this modified behavior, the noConflict support for JsRender had been removed. NEW FEATURES - observeAll() for cyclic objects is now supported for the vast majority of cases. See #304 - Improved support for data-linking to data- attributes: <elem data-link="data-foo{:expr}" ...>. After data-linking, the value of the data-foo attribute will be expr.toString(), but $.data(element, "foo") and $(element).data("foo") will actually return the value of expr, even if of type object. See #306 - Browserify Support: JsRender on Node.js provides a built-in Browserify transform - jsrender.tmplify, for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var $jsr = require('jsrender'); browserify(...) ... .transform($jsr.tmplify) ... See also http://www.jsviews.com/test/unit-tests-browserify.html - Initial work for deployment to Bower and NPM. See #254 BorisMoore/jsrender#225 Bug Fixes: - BorisMoore/jsrender#263 BorisMoore/jsrender#264 Caching of template on script elements. (Unit tests added) - #304 ObserveAll on cyclic objects - #306 'data-xxxx' attribute using data-link - #307 #312

BREAKING CHANGES AND IMPROVEMENTS - The global namespace when JsRender is loaded without jQuery is now window.jsrender. (Previously it was window.jsviews). So when using JsRender without jQuery, you can write: var $ = jsrender; - and use the $ var it in the same way you would use the global $ when JsRender is loaded with jQuery: e.g. $.templates(...) or $.views.helpers(...) etc. - AMD support has been improved and simplified. All AMD modules, including JsRender, with or without jQuery, now return the jQuery object (if loaded) or the analogous JsViews object. - Node.js support and integration has been improved - along with improved CommonJS support, and Browserify integration. The file system APIs now use the syntax tmpl="./file/path.html". The Node.js version of jsrender.js is available as a separate file (available at //jsviews.com/download/jsrender-node.js). The Node.js version of JsRender provides the complete set of JsRender APIs and features, together with integration with NodeJS view-engines such as Express and Hapi, APIs for loading templates from the file system, etc. The file system APIs now use the syntax tmpl="./file/path.html". It also includes a built-in Browserify transform (see "Browserify Support: below). (Note: JsRender and JsViews will soon be published to NPM). - The behavior when loading multiple instances of JsRender or JsViews files has been changed: When loading a new instance, the previous instance $.views, $.templates, etc. is no longer overwritten. So a component using JsRender or JsViews will not, when loaded, cause another already loaded component also using JsViews/JsRender to fail (except for collisions arising in the unlikely case where both happen to use the same template/converter/helper name). As part of this modified behavior, the noConflict support for JsRender had been removed. NEW FEATURES - observeAll() for cyclic objects is now supported for the vast majority of cases. See BorisMoore/jsviews#304 - Improved support for data-linking to data- attributes: <elem data-link="data-foo{:expr}" ...>. After data-linking, the value of the data-foo attribute will be expr.toString(), but $.data(element, "foo") and $(element).data("foo") will actually return the value of expr, even if of type object. See BorisMoore/jsviews#306 - Browserify Support: JsRender on Node.js provides a built-in Browserify transform - jsrender.tmplify, for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var $jsr = require('jsrender'); browserify(...) ... .transform($jsr.tmplify) ... See also http://www.jsviews.com/test/unit-tests-browserify.html - Initial work for deployment to Bower and NPM. See BorisMoore/jsviews#254 BorisMoore/jsrender#225 Bug Fixes: - BorisMoore/jsrender#263 BorisMoore/jsrender#264 Caching of template on script elements. (Unit tests added) - BorisMoore/jsviews#304 ObserveAll on cyclic objects - BorisMoore/jsviews#306 'data-xxxx' attribute using data-link - BorisMoore/jsviews#307 BorisMoore/jsviews#312

Added quick start documentation as README.md BREAKING CHANGES - One very minor breaking change: the $.views.compile(...) alias for $.templates has been removed from jsrender.js, but is still available for Node.js (e.g. for Hapi templates integration) as $.compile(...). NEW FEATURES - This version of JsRender will be published on NPM. Install using: $ npm install jsrender - Browserify Support: JsRender on Node.js provides a built-in Browserify transform for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var tmplify = require('jsrender/tmplify'); browserify(...) ... .transform(tmplify) ... See also http://www.jsviews.com/test/unit-tests-browserify.html - Continuing work for documentation/deployment to NPM. See BorisMoore/jsviews#254 #225 Bug Fixes: - #172

Replaces commits 66 and 67. Updated documentation. See also https://github.com/BorisMoore/jsrender-node-starter. BREAKING CHANGES - One very minor breaking change: the $.views.compile(...) alias for $.templates has been removed from jsrender.js, but is still available for Node.js (e.g. for Hapi templates integration) as $.compile(...). NEW FEATURES - This version of JsRender has been published on NPM. Install using: $ npm install jsrender - Browserify Support: JsRender on Node.js provides a built-in Browserify transform for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var tmplify = require('jsrender/tmplify'); browserify(...) ... .transform(tmplify) ... See also https://github.com/BorisMoore/jsrender-node-starter, and http://www.jsviews.com/test/unit-tests-browserify.html - Continuing work for documentation/deployment to NPM. See BorisMoore/jsviews#254 #225 Bug Fixes: - #172

Updated documentation. See also https://github.com/BorisMoore/jsrender-node-starter. and https://github.com/BorisMoore/jsrender. BREAKING CHANGES - One very minor breaking change: the $.views.compile(...) alias for $.templates has been removed from jsrender.js, but is still available for Node.js (e.g. for Hapi templates integration) as $.compile(...). NEW FEATURES - JsRender is now published on NPM. Install using $ npm install jsrender - Browserify Support: JsRender on Node.js provides a built-in Browserify transform for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var tmplify = require('jsrender/tmplify'); browserify(...) ... .transform(tmplify) ... See also https://github.com/BorisMoore/jsrender-node-starter, and http://www.jsviews.com/test/unit-tests-browserify.html - Continuing work for deployment to NPM. See #254 BorisMoore/jsrender#225 Bug Fixes: - BorisMoore/jsrender#172

Updated documentation. See also https://github.com/BorisMoore/jsrender-node-starter. and https://github.com/BorisMoore/jsrender. BREAKING CHANGES - One very minor breaking change: the $.views.compile(...) alias for $.templates has been removed from jsrender.js, but is still available for Node.js (e.g. for Hapi templates integration) as $.compile(...). NEW FEATURES - JsRender is now published on NPM. Install using $ npm install jsrender - Browserify Support: JsRender on Node.js provides a built-in Browserify transform for including compiled JsRender templates from the server, as part of the client javascript bundle generated by Browserify. Usage example: var tmplify = require('jsrender/tmplify'); browserify(...) ... .transform(tmplify) ... See also https://github.com/BorisMoore/jsrender-node-starter, and http://www.jsviews.com/test/unit-tests-browserify.html - Continuing work for deployment to NPM. See BorisMoore/jsviews#254 BorisMoore/jsrender#225 Bug Fixes: - BorisMoore/jsrender#172

BorisMoore · 2015-09-02T05:57:36Z

JsRender has now been published to NPM and Bower, and includes Browserify support with a transfrom jsrender/tmplify. See https://github.com/BorisMoore/jsrender-node-starter

Moving to #174 for tracking publishing of JsRender and JsViews to webjars, composer, typescript... - and registering in jQuery plugins registry also...

badiezadegan changed the title jsviews seems incompatible with **browserify** jsviews seems incompatible with browserify Apr 20, 2014

BorisMoore added the Planned for V1 label Apr 23, 2014

badiezadegan closed this as completed Apr 24, 2014

BorisMoore reopened this Apr 24, 2014

BorisMoore closed this as completed Sep 2, 2015

BorisMoore added Resolved and removed Planned for V1.1 labels May 2, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

jsviews seems incompatible with browserify #254

jsviews seems incompatible with browserify #254

badiezadegan commented Apr 20, 2014

BorisMoore commented Apr 21, 2014

badiezadegan commented Apr 23, 2014

gbouthenot commented Apr 23, 2014

BorisMoore commented Apr 23, 2014

badiezadegan commented Apr 24, 2014

BorisMoore commented Apr 24, 2014

BorisMoore commented Sep 2, 2015

jsviews seems incompatible with browserify #254

jsviews seems incompatible with browserify #254

Comments

badiezadegan commented Apr 20, 2014

BorisMoore commented Apr 21, 2014

badiezadegan commented Apr 23, 2014

gbouthenot commented Apr 23, 2014

BorisMoore commented Apr 23, 2014

badiezadegan commented Apr 24, 2014

BorisMoore commented Apr 24, 2014

BorisMoore commented Sep 2, 2015