Investigate and potentially remove dependencies on browser-only APIs

[mstade]

From @mstade on September 18, 2015 13:37

Currently, nap depends on at least window.document.matchesSelector but possibly others as well. This dependency causes some issues in supporting execution in both server side and client side contexts, and should possibly be removed altogether. If it can't be removed, care must be taken not to include superfluous dependencies in client side contexts.

Copied from original issue: sammyt/nap#21

[mstade]

@websdk/contributors is anyone using the nap.is API? I'm keen to remove it otherwise, it'd reduce nap's exposure to browser APIs, and limit it to the matches check in bySelector.

[aaronhaines]

I don' think so, but I'll check and get back to you

[mstade]

Much obliged @aaronhaines!

[sammyt]

Ah yes, browser dependencies. Would be nice if there was an easy way to include/exclude platform specific extension like this. I just put everything in one file, because, well, files.

[sammyt]

Also, as I recall it made my life much harder when I was trying to get this to run in node, but I guess no one is doing that at the moment(?), but could well be valuable.

[mstade]

I've got #10 running in node. Removing the dependency on window did the trick, but it obviously fails if you don't have something DOM-y to run views against. Probably fair, and not unlike how for example d3 deals with things.