Bower artifact management (Archive-package instead of GitURL-package)

Good morning,

We are currently using Proget for Bower repositories (and also Nuget and NPM).
We realize that the current standard for Bower repositories is close to simply link a package name to the corresponding git repositories URL, but for various reasons (ease of automation for CI and CD, tracability, separation of source management and artifact management, etc) we are wondering if and when you would change the way you manage Bower artifact to an Archive-package manner. i.e. .zip .tar.gz packages.

Inspiring ourselves from the way Artifactory is managing Bower packages (creating a custom bower resolver, publishing a .tar.gz file) we were able to create a working proof of concept in around a week, so I'm pretty sure you guys would not have any problems implementing it.

Thank you and have a nice day

Product: ProGet
Version: 4.0.15

Hi François,

You're right, it'd be ideal if Bower supported packages instead of just being a pointer to a Git repository... we simply weren't able to think of a good way to solve this problem, though it seems like the recent addition of custom resolver might be a solution? Still not sure how...

Have you seen the ProGet Universal Packages/Feeds? Do you think a custom resolver to a repository like that could work?

Here is a solution for you guys :
We implemented two open source tools that allow using bower package-based artifacts based on Alana's previous comment. They are still in active early development, but we are currently using them in our day to day work.

##Bower client
https://github.com/WoltersKluwerCanada/proget-universal-bower-client

This tool is packaging bower repositories into a .upack file
It can also deploy to a proget repository

##Bower resolver
https://github.com/WoltersKluwerCanada/proget-universal-bower-resolver

This tool is an extension to bower which resolves/unpackages upack-proget feeds as bower feeds.