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

Issue installing/resolving bower package after updating to 0.1.3 #2591

Closed
jcope2013 opened this issue Nov 30, 2014 · 12 comments · Fixed by #2821
Closed

Issue installing/resolving bower package after updating to 0.1.3 #2591

jcope2013 opened this issue Nov 30, 2014 · 12 comments · Fixed by #2821

Comments

@jcope2013
Copy link
Contributor

I updated to 0.1.3, followed all the instructions properly but now when I run ember serve I see this

Joshuas-MacBook:inbox-dashboard jcope$ ember serve
version: 0.1.3

Missing bower packages: 
Package: ember-easyForm
  * Specified: http://builds.dockyard.com.s3.amazonaws.com/ember-easyForm/canary/ember-easyForm.js
  * Installed: (not installed)

Run `bower install` to install missing dependencies.

its a url in my bower.json

 "ember-easyForm": "http://builds.dockyard.com.s3.amazonaws.com/ember-easyForm/canary/ember-easyForm.js",

and referenced like this in my brocfile.js

  app.import('bower_components/ember-easyForm/index.js');

running bower install and then running ember serve will keep giving me this error but yet bower seems to be getting it properly and downloading the file in an ember-easyForm folder under my bower components, so it seems for some reason, it now isn't able to detect that its installed when it really is, this was working under 0.1.2

A fix I made was just moving the file in my vendor folder and reference it in my Brocfile.js under that location and delete the corresponding bower folder and reference in bower.json, and now the app starts fine.

I am wondering what the regression was or if this isn't possible anymore to reference links like this in bower.json

@rwjblue
Copy link
Member

rwjblue commented Nov 30, 2014

@quaertym - Can you take a look here? I believe that this is related to quaertym/ember-cli-dependency-checker#12.

@rwjblue
Copy link
Member

rwjblue commented Nov 30, 2014

@jcope2013 - You can remove ember-cli-dependency-checker from your package.json to resolve the issue for now...

@jcope2013
Copy link
Contributor Author

@rwjblue okay thanks

@rwjblue
Copy link
Member

rwjblue commented Nov 30, 2014

I'd like to keep this open until we get this fixed upstream.

@chrmod
Copy link
Member

chrmod commented Dec 3, 2014

got exactly same problem with number of bower dependencies: harvesthq/chosen, jamiebikies/ember-pusher

@stefanpenner
Copy link
Contributor

For reference my solution/workaround was to merely "vendor" this dependency and commit it to my project manually. Thereby bypassing the dependency checker for this issue, but still getting the benefit for other packages.

@sohara
Copy link
Contributor

sohara commented Dec 4, 2014

Same issue for 'csantero/ember-sinon'....

@habdelra
Copy link

habdelra commented Dec 6, 2014

ditto on 'ebryn/ember-console-utils' ... (non PAAM project @rwjblue)

@rwjblue
Copy link
Member

rwjblue commented Dec 7, 2014

@habdelra - Suggested work around for now is to remove ember-cli-dependency-checker from the blueprint. I would really like a solution here though.

@quaertym - Have you had a chance to take a look and address this?

@quaertym
Copy link
Contributor

quaertym commented Dec 8, 2014

@rwjblue Had a very busy week, it is definitely on my schedule.

@stefanpenner
Copy link
Contributor

@quaertym thanks :)

@AmilKey
Copy link

AmilKey commented Dec 8, 2014

@quaertym This problem also occurs if Library in a local folder

"group-helper": "./vendor_without_bower/group_helper/main.js",

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

Successfully merging a pull request may close this issue.

8 participants