I just stumled about the
packages-for-everything approach and like the idea of creating reusable components and organizing my code this way.
BUT having a look at the telescope example-project (https://github.com/TelescopeJS/Telescope)
it seems to me that I am stacking up my workload and I make my workflow more complex?
The project I am working on is quite complex and could need a good structure.
so i guess right now it is good for me to keep things simple. KISS.
My [newbie] assumptions are (please correct me if I am wrong)
- I’ll have to manually define each single file (including directory names) used within each package
- I’’ have to define package dependencies (including my standard set of standard-3rd-party-apps) in each package
- I’ll have to run
meteor updatemanually for each package and maybe even update version-numbers of those dependency for each package
- I’ll end up with A LOT of packages (telescope has 37 packages to manage). Adding 1 package means adding another round of steps 1-3…
- I wonder: Will testing my packages work with velocity:jasmine?? This is really important for me
My questions to the experts are:
a) Would you recon this structure for a single-programmer working alone on a medium-complex project
b) Are there tools available to help me managing all those packages? (see steps 1-3)
c) Does testing work will with this structure? Right now I am sticking my head into velocity:jasmine
d) Will debugging work well?
e) Is there anything else to considerß
I’m really looking forward to your feedback