jongleberry

@dougwilson you mean something like ``` js // require() style import types from 'mime-db/types.json' import extensions from 'mime-db/extensions.json' // all at once import { types, extensions } from 'mime-db' //...

i don't mind breaking changes :D

either one is fine for me. how do you handle "default" mime types, though? just the first extension?

oh fuck. what i want to know is, "what is the default extension for a mime type?"

okay cool. that's all i'm worried about, so i would opt for num 1 unless num 2 handles that.

what would ew call this field? `encoding`? some values: - `text` - `binary` - `['text', 'binary']`?

i'm wondering how we would name this field and how to represent all the possible values as @Fishrock123 stated

oh. that's not what i think of when i read "representation".

so shall we use `representation` or what? i think it should be `encodings` or something. otherwise, we can delay this until after v1 since it shouldn't break anything

i'm assuming node has one that we should follow, no? would make things simpler yeah, i'm :+1: with standard or airbnb or whatever as long as there is one. `eslint...