Breaking apart files

[mmcc]

Placeholder for tracking changes related to breaking apart files such as lib and any other file with multiple components within.

[heff]

I think I can include breaking up the Components in #1993, though it might make it hard to read the specific ES6 Class diffs if a lot of things are in new files.

[heff]

#1993 broke up component classes into their own files. Still need to address lib.

[dmlap]

Remaining

• Break up lib.js into sensible categories
• Wrap in util.js into that work

[dconnolly]

I can take this.

[heff]

@dconnolly did you get anywhere with this that I could take a look at? I started taking a pass at this myself.

[heff]

Is there a common way of naming utility library functions when they're pulled into a script individually, so that it's clear they've been pulled in?

For example pulling in createEl from the dom.js util library. I don't love that I might use createEl() somewhere in the code and it looks like any other function that may have been created in that file. Especially in the case of createEl and Component where we're creating a component.createEl() function that uses createEl internally. It gets ambiguous.

ping @gkatsev, @mmcc, @dmlap

[dconnolly]

@heff I did not, spent most of my time on videojs/videojs.com

[heff]

@dconnolly Cool, no worries. Thanks.

[heff]

Closed by #2139