currently we are looking into using bower instead of ender in our client side javascript projects. We are therefore evaluating different alternatives to replace the require/provide glue code generated by ender. Browserbuild appeals to us mostly because of its light weight approach and low complexity while more or less providing the same api our code base already uses.
However, some small additions might be required to make the transition as smooth as possible. I'd like to check with you, whether these features are something you would like to see in browserbuild. If so, I'll consider preparing a pull request.
The way I imagine browserbuild to be used in conjunction with bower is to leverage bower´s list --paths feature. Basically, it allows to determine a hash of main source files indexed by package names. Inside our code we would like to require libraries by these package name. It would therefore be necessary to register dependent library files by a specified name rather then by their exact file name. For example we would like to call require('mylib') instead of require('components/mylib/dist/mylib.js'). I could imagine a grunt plugin combining the strengths of bower and browserbuild, if the browserbuild api allowed files to be registered by explicitly given names.
I want to emphasize again, that it is not my plan to make browserbuild depend on bower in any way. But with this simple addition, the two could be used together while keeping their UNIX-philosophy style focus.
Hi,
currently we are looking into using bower instead of ender in our client side javascript projects. We are therefore evaluating different alternatives to replace the
require/provideglue code generated by ender. Browserbuild appeals to us mostly because of its light weight approach and low complexity while more or less providing the same api our code base already uses.However, some small additions might be required to make the transition as smooth as possible. I'd like to check with you, whether these features are something you would like to see in browserbuild. If so, I'll consider preparing a pull request.
The way I imagine browserbuild to be used in conjunction with bower is to leverage bower´s
list --pathsfeature. Basically, it allows to determine a hash of main source files indexed by package names. Inside our code we would like to require libraries by these package name. It would therefore be necessary to register dependent library files by a specified name rather then by their exact file name. For example we would like to callrequire('mylib')instead ofrequire('components/mylib/dist/mylib.js'). I could imagine a grunt plugin combining the strengths of bower and browserbuild, if the browserbuild api allowed files to be registered by explicitly given names.I want to emphasize again, that it is not my plan to make browserbuild depend on bower in any way. But with this simple addition, the two could be used together while keeping their UNIX-philosophy style focus.
Best Tim