Library not accessible via bower as a bower component about formio.js

[Csini]

can you please publish this library to bower?

[travist]

I am willing to do this, but I am curious what you get out of bower that you do not get with npm. Historically we used bower in combination with wiredep, but this library would never need that. Also, some of the dependencies of this library also do not support bower (like signature-pad). I think that bower is going away but would like to hear from you your thoughts.

[Csini]

I would like to use and customize (simplify) your ng-form-builder. It has formio.js as an npm dependency. I have to work with a strict company framework, which has a strict gulp build process, based on, that all the dependencies are bower components, and in npm we only have the "build tools" as devDependencies like gulp, bower, ... Our system is not prepared for dependencies in npm :(

[Csini]

the main problem is with the dependencies from formiojs
for example: lodash
I have it in my spa as a bower dependency -> it makes versioning problems if I have it in npm and bower tooo
that's why I would like to have all the dependencies only in bower

[Csini]

I only need via bower a

• transpiled (ES5)
• derequired
• ready-to-use
• distribution version

from your formio.js source

[travist]

This is now accessible with bower. thanks.

[Csini]

THANK YOU!