Today @danmactough raised a question about entire_module dependencies vs node_modules dependencies. In general I'm thinking of Entire as extending the node_module system to the browser, but I had kept entire_modules different from node_modules because it is easier to know what should be in the koa stack if its in a folder just for it. Obviously, this is not a good enough reason.
Included in this gist are three files. Two entire_module package.json files, saved in some likely named folder in the node_modules folder and a standard node_module package.json file, defining the dependencies of my first entire app.
- By including the two
entire_modulesandentireitself into the app's package.json file, we enable the usage of npm for installingentire_modules. - By making
entirea possible param on anode_modulepackage.json, we give a way to tell what modules are forentireand which ones aren't. - By changing
dependenciestoextendingunder theentireparam of the package.json, we drawn a line between howentire_modulesdepend on otherentire_moduleswhile still keeping the default node.js dependency flow in place.
- By moving
entire_modulesdependencies out ofdependenciesand intoextending, we open up the problem of vetting versions and complacate checking for the exhistance of said dependencies.