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

Remove moot version property from bower.json #455

Closed
wants to merge 1 commit into from
Closed

Remove moot version property from bower.json #455

wants to merge 1 commit into from

Conversation

cvrebert
Copy link

@cvrebert cvrebert commented Jun 4, 2015

@necolas
Copy link
Owner

necolas commented Jun 10, 2015

i think i'll just drop explicit bower support next release

@cvrebert
Copy link
Author

👏 👏 Sounds good 👍

@necolas necolas closed this in 8cfa3e7 Jan 5, 2016
@cvrebert cvrebert deleted the patch-1 branch Jan 5, 2016
@cvrebert
Copy link
Author

cvrebert commented Jan 5, 2016

I salute your bravery sir. 🎖 Stay strong against the inevitable backlash. ❤️

@alexwilczewski
Copy link

Take this post as curiousity, not as "the inevitable backlash". What is the reason to remove bower support? Is it because with bower you can explicitly reference the git repo?

@FagnerMartinsBrack
Copy link

Take this post as curiousity, not as "the inevitable backlash". What is the reason to remove bower support? Is it because with bower you can explicitly reference the git repo?

There is no need for bower.json since you can download the whole repository and run the builds programatically. Also, the community seems to be slowly dropping bower in favor of npm.

The inevitable backslash seems to be from the ones that rely in some features from bower.json like the files that are ignored through the ignore array, the license config (where some tools use to audit the dependency licenses), the main property that maps the main file, etc.

@olach
Copy link

olach commented Feb 11, 2016

Sad to see Bower support go away. I don't agree that this is the way to go. But I understand that having to support multiple package managers takes some time.

I know I'm still able to fetch packages with Bower directly from the Github repo. So I can still use Bower. But I really don't understand those who prefer to use npm instead of Bower.

IMHO npm is only for Node packages. I use it mostly for all build scripts. It just feels wrong to keep front end assets like css-files in the node_modules folder, together with mostly development/server code and build scripts.

In some projects, its also useful to commit Bower components into the repo.

I guess the chances to re-add Bower support is minimal, so I don't open a new issue on this topic, but I write here in this thread to express my opinion on this topic. Not all of us developers likes the current trend of moving away from Bower to npm.

@ctrlmaniac
Copy link

@olach 👍 👍 👍
I use npm for tests and task runners, and bower for clean, pluggable, front-end packages like normalize.css. Also it has not to be maintained like npm (you don't have to npm publish every time). So you could have kept it and made everybody happy 💔

@battaglr battaglr mentioned this pull request Mar 14, 2016
lkraav added a commit to lkraav/pure that referenced this pull request Nov 27, 2016
lkraav added a commit to lkraav/pure that referenced this pull request Aug 29, 2017
lkraav added a commit to lkraav/pure that referenced this pull request Dec 16, 2017
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 this pull request may close these issues.

None yet

6 participants