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.

Sign up for GitHub

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

Jump to bottom

Remove moot version property from bower.json #431

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Remove moot version property from bower.json #431

wants to merge 1 commit into from

Conversation

kkirsche
Copy link

@stoeffel
Copy link
Collaborator

Intended to be used in the future when Bower gets a real registry where you can publish actual packages, but for now just leave it out.

As far as I understand it will be used again in the future.
Is there a problem with just leaving it in there? If we really need to remove it, we would also have to change the gulpfile (see gulpfile.js#L15) because we automatically update the version in the bower.json.

@kkirsche
Copy link
Author

Considering bower core development is basically dead, I would strongly recommend focusing on NPM, not on Bower.

@stoeffel
Copy link
Collaborator

That's why I don't care if there is a moot attribute in there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@kkirsche @stoeffel