.. is a module i built to manage dependencies in complex projects where files can be spread over different folders.
At my company we write applications that heavliy depend on inheritance. So most of the time i may have a structure like this:
+-- coreProject
+-- childProjectA
+-- childProjectB
+-- childProjectBCore
+-- childProjectBChildA
+-- childProjectBChildACore
+-- childProjectBChildAChild
+-- childProjectBChildB
..
Each project may or may not inherit from its parent or neighbour project. It also may or my not have sources that also are available in parent or neighbour projects.
What i needed was something that allows me to collect sources the projects might depend on for css and javascript builds which i do locally or on build environments.
Lets assume we have this kind of structure for some applications that should inherit from each other:
+-- coreProject
+-- js
+-- lib
+-- src
+-- moduleA
+-- moduleB
+-- css
+-- lib
+-- src
+-- moduleA
+-- moduleB
+-- childProjectA
+-- js
+-- presets
+-- css
+-- variables.css
+-- default.css
+-- childProjectB
+-- js
+-- presets
+-- src
+-- moduleC
+-- css
+-- lib
+-- src
+-- moduleA
So the core project on the top leve serves as the core library. Each client project can also have a core project that its descendants depend on. In the end the child projects should have a minimum of the application logic as long as they dont want to override something. The only thing they provide in my case is something like configuration for the libraries they depend on (represented by the folder 'presets' here)
So given something like this , how can we collect our files without throwing up?
Currently you need to clone this repository. Im planning on publishing it on npm when im done with the things i think are missing. Until then
$ git clone https://github.com/juicyarts/fs-inheritance-lib
They are not yet at 100% but:
- Use js standard style
- Write tests!
- 0.1.0 Initial release