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

Update bower.json to comply with new spec for main #16359

Merged
merged 2 commits into from
Apr 24, 2015
Merged

Update bower.json to comply with new spec for main #16359

merged 2 commits into from
Apr 24, 2015

Conversation

cvrebert
Copy link
Collaborator

This updates our bower.json to comply with the new, long-awaited, more detailed spec for the main field of bower.json. See bower/spec#43

If you have a complaint about this, take it up with the Bower folks, not us:
https://github.com/bower/bower.json-spec/issues
Or consider using a different package manager.

Per bower/spec#43 :
> font files [...] are not `main` files as they are not entry-points.

If you have a complaint about this, take it up with the Bower folks:
https://github.com/bower/bower.json-spec/issues
Per bower/spec#43 :
> Use source files with module exports and imports over pre-built distribution files.

Also, the example in that PR doesn't include
/dist/movement.css or /dist/movement.min.css
in its `main`.

If you have a complaint about this, take it up with the Bower folks:
https://github.com/bower/bower.json-spec/issues
@cvrebert cvrebert added the meta label Apr 24, 2015
@cvrebert cvrebert added this to the v3.3.5 milestone Apr 24, 2015
@twbs twbs locked and limited conversation to collaborators Apr 24, 2015
cvrebert added a commit that referenced this pull request Apr 24, 2015
Update bower.json to comply with new spec for `main`
@cvrebert cvrebert merged commit 1c57181 into master Apr 24, 2015
@cvrebert cvrebert deleted the bower branch April 24, 2015 17:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants