raphamorim / inphinity Goto Github PK

Hey, nice project...

Today you export 2 global variables, the Contructor Inphinity and the instance inphinity. Should them both be in the global scope? maybe if you wrap everything into an IIFE you can only export the one that's actually gonna be used by the developer.

Also you can add UMD support on it, adding a simple snippet, or even add it to your build process (which is nicer in my opinion)

Cheers!

Browser Chrome Version 45.0.2454.101 (64-bit)
Platform: OSX Yosemite 10.10.5

How to reproduce

• Access http://raphamorim.com/blog/ && Open DevTools
• Scroll to down
• Click Next

Console outputs this message

Inphinity: Sorry, we couldn't parse your Next (Previous Posts) URL.

Possible solutions:

• Use ES6 (using babel and other tools)
• realize a call of the current function inside passing context

Why?
Reduce project size, pls. te-hehe

What about use DocumentFragment to include new Elements to DOM? We can increase performance on the DOM Manipulation.

Reference: #7

I'm able to suggestions :)