You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently still using bower as a front end library manager. I am also using stealJS as a module loader and bundler. stealJS when using repo's bower.json file to define dependency graph uses the bower.json file in each bower library. The bower.json file doesn't exist which causes an error. I could see an argument for submitting an issue with stealJS to use the .bower.json file that is created when a library is install via bower command line but thought i'd start here
The text was updated successfully, but these errors were encountered:
@domenic and I are pretty strongly against maintaining >1 package manifests. If anything, this is an opportunity to put pressure on bower to get on board the package.json train.
I am currently still using bower as a front end library manager. I am also using stealJS as a module loader and bundler. stealJS when using repo's bower.json file to define dependency graph uses the bower.json file in each bower library. The bower.json file doesn't exist which causes an error. I could see an argument for submitting an issue with stealJS to use the .bower.json file that is created when a library is install via bower command line but thought i'd start here
The text was updated successfully, but these errors were encountered: