(NOTE: This was moved from another topic)
Oh ok sorry, it was worded as if I was on Stack Overflow(I have had some bad experiences on SO at times so its still frustrates me even after many years later). I appologize for responding like that, but if I saw the reason prior I would of gave a better reply.
(I hope I don’t bore you with my long explanation, but I want to say this so that way I can get my point about my ideas about your project)
But as far as your project, after reviewing your code and readME; I love what you have done so far. Actually I have been wanting to start working in open source to help me learn.
Not getting off topic here(I am trying to make a point with this by telling you my experiences), I am currently taking a summer coarse called "Internet Computing at my college taught by a wonderful professor. Though after 5 days of going to class and staying up all night to meet the deadline for a code review I thought of something.
After watching my fellow classmates strugle with build tools like grunt and nodeJS/npm, I came to this realization that their is a problem with this. The high entropy of possibilities/packages/plugins/generators can make a beginners head explode if I utter the word “packages” and "dependencies.
I try to help my classmates as much as I can despite my busy schedule. Basically everyone emails me and the professor every day but the most I have seen are about build tools and packages. They aren’t as confused with the code, but they are confused about why APM or NPM exists.
[Ok here’s my idea below just incase of cltl;dr]
So I am kinda of though of what if we could fix that complexity. I dont want it to become just another package manager. I wanted something to easily manage those package managers. So say we have a package.json just chilling in the global directory. Well why is there just one package.json folder??? Why cant there be many of them which are labeled for the builds and dependencies we would like in certain projects. Wouldnt that be faster than just:
npm install this that thenThis moreCrap okTooMuchCrap
Which has got me thinking of what if I could just take your idea of syncing configurations with my own. Could I be able to make something to sync a set of configs in which are used for different purposes. By basically making managing the manager itself. They are called packages for Pete Sake why can’t we pack the packages? I feel like maybe my idea is a good place to start because yes you can sync your configs, but why not as well sync many different configs. It may be a feature you can make optional.
Now I have to admit even though I have done alot in Web Development but I really want to learn through contributing to the community. With the goal set to make it more easier/better for inexperienced people to learn. That is my goal is to help developers become lazier by saving a few min time.
I am not experienced in making build tools so if you’d like to discuss this somewhere else since we are getting off topic: here is my email: www.matthew-dickens.com
I apologize for any bad grammar since I am both coding and typing this at the same time.
Again thank you!