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

define asset-type properties #21

Closed
necolas opened this issue Feb 26, 2014 · 5 comments
Closed

define asset-type properties #21

necolas opened this issue Feb 26, 2014 · 5 comments

Comments

@necolas
Copy link

necolas commented Feb 26, 2014

for example: styles, scripts, fonts, images. without these, it makes life difficult for tools to have any useful information that defines the component contents

@apobbati
Copy link

apobbati commented Mar 4, 2014

Any takers on this?

@benschwarz
Copy link
Member

Yeah… it feels like we've covered this many times… my only concern is if we reserve certain keys, what should they be?


Packages probably shouldn't be shipping un-compiled (scss, less, coffeescript assets) because they're not immediately useful to anyone.

Perhaps we aim for anything that can be directly linked from a HTML document. That is:

images, fonts, videos, stylesheets and scripts

@unscriptable
Copy link

I agree that it would be useful to have more granular information about assets.

@benschwarz, I disagree with this statement:

Packages probably shouldn't be shipping un-compiled (scss, less, coffeescript assets) because they're not immediately useful to anyone.

There are very good use cases for compiling scripts, modules, scss, etc. in the context of the application's source code. Therefore, I wouldn't limit the list to compiled assets.

@benschwarz
Copy link
Member

@unscriptable Ok. Lets not have that argument in this thread though ⛵

@desandro
Copy link
Member

Closing here and moving to new issue #47.

@bower bower locked and limited conversation to collaborators Jun 22, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

5 participants