Closed dphochman closed 7 years ago
Can't deny that bower is still pretty popular. But, that sounds like another project of it's own. Wouldn't want to add that to this repo.
What do you think?
Of course, you are correct. Small pieces loosely joined...
If it's OK with you to fork or require "cost-of-modules" to jumpstart a "cost-of-packages" or "cost-of-bower" package, that's the route I'll pursue. If it works, I may attempt to register it on bower.io. And that may lead me or others to enter the above-mentioned vortex.
Thank you for this work.
@dphochman Of course! Go for it!
In my app (based on angular-seed), the runtime dependencies are installed by
bower install
which is triggered by npm scriptpostinstall
, and not detected by cost-of-modules.bower.json
declares the runtime dependencies, and.bowerrc
declares the directory where the dependencies are installed (the default directory isbower_components/
).I realize that this request may lead to a vortex of unreachable goals, such as a deep understanding of the impact of specific npm scripts, obscure options in bower, or supporting other package managers. Perhaps each of those can be prioritized and tackled independently. AFAIK, using bower for runtime dependencies is a popular practice.