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

Remove bower install from npm install script #179

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
5 participants
@timmywil

timmywil commented Jul 11, 2014

For those of us using npm as the front-end package manager, forcing a bower install throws a wrench in the gears. I'd much rather be responsible for installing these dependencies myself.

@kapouer

This comment has been minimized.

Show comment
Hide comment
@kapouer

kapouer Sep 27, 2014

You could at least use bower install || echo "fullcalendar is best installed using bower"
to avoid failure upon install.

kapouer commented Sep 27, 2014

You could at least use bower install || echo "fullcalendar is best installed using bower"
to avoid failure upon install.

@samedii

This comment has been minimized.

Show comment
Hide comment
@samedii

samedii Sep 27, 2014

Why is forcing the use of bower when developing/building a problem for you?

samedii commented Sep 27, 2014

Why is forcing the use of bower when developing/building a problem for you?

@kapouer

This comment has been minimized.

Show comment
Hide comment
@kapouer

kapouer Sep 27, 2014

When doing npm install https://github.com/arshaw/fullcalendar/archive/v2.1.1.tar.gz you are not necessarily in an environment where bower is available, so if having bower is a hard requirement, please add it to dependencies ? But that looks like forcing that package manager upon the users, when they not necessarily feel confortable with it - especially if they are using npm !

kapouer commented Sep 27, 2014

When doing npm install https://github.com/arshaw/fullcalendar/archive/v2.1.1.tar.gz you are not necessarily in an environment where bower is available, so if having bower is a hard requirement, please add it to dependencies ? But that looks like forcing that package manager upon the users, when they not necessarily feel confortable with it - especially if they are using npm !

@samedii

This comment has been minimized.

Show comment
Hide comment
@samedii

samedii Sep 28, 2014

My point is that, as far as I know, I didn't need to use bower at all unless I wanted to run the demos

samedii commented Sep 28, 2014

My point is that, as far as I know, I didn't need to use bower at all unless I wanted to run the demos

@kapouer

This comment has been minimized.

Show comment
Hide comment
@kapouer

kapouer Sep 28, 2014

that's precisely the point: it is needless to have bower called in package.json's scritps.install

kapouer commented Sep 28, 2014

that's precisely the point: it is needless to have bower called in package.json's scritps.install

@samedii

This comment has been minimized.

Show comment
Hide comment
@samedii

samedii Sep 29, 2014

Ok, I get your point

samedii commented Sep 29, 2014

Ok, I get your point

@dansomething

This comment has been minimized.

Show comment
Hide comment
@dansomething

dansomething Dec 11, 2014

I'm running into the same issue and would love to have this merged in rather than maintaining my own fork.

dansomething commented Dec 11, 2014

I'm running into the same issue and would love to have this merged in rather than maintaining my own fork.

@arshaw

This comment has been minimized.

Show comment
Hide comment
Member

arshaw commented Mar 9, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment