Migrate to jQuery & NPM

[marlowpayne]

Reviewers: @fractaltheory @jansepar @mikenikles @MikeKlemarewski

Changes

• First pass at cleanup / standardizing plugins around jQuery and NPM
• Migrate Zepto to jQuery
• Migrate Bower dependencies to NPM
• Migrate Velocity.js from Mobify's fork to latest proper release
• Update the README and CHANGELOG
• Pin versioning in package.json
• Fix naming of event-polyfill
• Migrate JS source code linting to current standards (eslint)
• Migrate SCSS compilation to current standards (libsass)
• Add SCSS linting

  Todos:

• [x] +1
• [x] +1 (Second +1 because this might require a bump to major version)

  How to Test

• Checkout code
• rm -rf node_modules && npm install
• grunt test or grunt test:browser
• Proofread the changes to the README

[mikenikles]

Nice work, @marlowpayne!

I agree that we're looking at a major version bump here. Should we add a note to the README to let people know Zepto support is available up until v2.0.3? In case someone relies on Zepto and wants to use Pinny.

[MikeKlemarewski]

This is looking pretty great! My one question would be: what happens when I require in Pinny to my adaptive project and they depend on different jQueries? I bet I'll get two jQueries in my bundle which seems a bit wasteful. It would be sweet if we could give the option to BYO jQuery

[marlowpayne]

Great question @MikeKlemarewski ! Someone please correct me if I'm wrong here, but I am pretty sure Pinny is already flexible to the version of jQuery that it binds to. We first bind to require's version of $ (which can be set from the project's require config), but failing that we bind $ to window's Zepto or jQuery.

The only time we bind to our NPM version of jQuery is when we set up our examples and tests.

[highruned]

That's correct @marlowpayne. Well, almost. If it's being built in an AMD environment (eg. our Require.js builds), our standard plugins bring in $ as whatever package we define $ to be, which is usually jQuery and used to be Zepto. If you don't define a $, it's not going to fall back, it's going to error out. If it's being run in the browser with no AMD environment (it is possible you could with browserify, etc.), we assume you are bringing in your own selector library and have a window.Zepto or window.jQuery defined.

I'm wondering if we might as well just drop that window.Zepto check, or at least make it secondary to the window.jQuery check?

[marlowpayne]

@ericmuyser, since this'll be a major version bump I'm fine with scrubbing all checks and references to Zepto in the code.

[marlowpayne]

Let's test out these changes on an in-flight project using jQuery and Pinny.

[highruned]

I'm cool with us using it in our project if you want to put it in sometime this week @marlowpayne :+1:

[jansepar]

:+1: ! If we haven't already, let's prep a release (and remember to use our branching strategy to do so :) )

[mikenikles]

:+1: from me as well. I tested that on a current project and confirm the upgrade works.