Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bower.json file not in root directory #824

Open
ej020586 opened this issue Dec 1, 2017 · 1 comment
Open

bower.json file not in root directory #824

ej020586 opened this issue Dec 1, 2017 · 1 comment

Comments

@ej020586
Copy link

ej020586 commented Dec 1, 2017

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

@kriskowal
Copy link
Owner

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants