Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Package Orchestra components separately so custom builds can be created #25

Open
alexnewmannn opened this issue Feb 23, 2016 · 0 comments

Comments

@alexnewmannn
Copy link

One issue with Orchestra is the size of it and the amount of 'bulk' it brings if you don't want to use all components.

I should be able to use $, Syphon, Radio and Marionette without having the full dist file; this would be applicable for being put through a browserify stream (with babel we can import only specific things, true) and when loaded on the page as a lib file (i.e from a CDN or just from the node_modules).

Using this over Backbone, Marionette, jQuery and Syphon alone means I CAN add to the build as and when I want, wont need to update my dependencies, I can simply rebuild my js file.

One way to do this could be how lodash does it and create an orchestra-modularised package, where you can import specific things in your package.json like orchestra-syphon and orchestra-radio.

Another could be to declare the requirements in the package json, similar to browserify transforms:

{
   "orchestra": [
     "syphon",
     "radio"
     "$"
   ]
}

doing this would only import and export the above namespaces to the new dist file.

Open to suggestions for any other ways,
let me know what you think

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant