Fix AMD loading issues for Vendor and Helper Scripts

[larsonjj]

Moved vendor and helper scripts above require.js script.

This helps alleviate issues where loading libraries like Backbone.js causes Mismatched anonymous define() module errors.

[moustachedelait]

I'd like this too

[its-danny]

Since this is fairly old and hasn't happened yet, I went ahead and made a fork.

https://github.com/dannytatom/grunt-template-jasmine-requirejs

[lukeapage]

@cloudchen Please could you merge or give rights to someone else (@dannytatom) to take over this on npm?

[cloudchen]

Sorry for the late responding. v0.2.1 is just released. Have a try and let me know if it not goes well.

[lostthetrail]

@cloudchen I am not sure if you are trying to adhere to semvar, but if so, this is a major release change. It is definitely not backwards compatible.

EDIT: Ah, you are on 0 major version. Scrap the above.

We are using the pre-PR functionality to declare mock modules (amd).

Likely this change should have created a new functionality, which would be above the require and have left the current functionality alone.

Can we get a revert?

[cloudchen]

It was my mistake. This PR shouldn't be merged and released.
I figured out compromise to this issue that load vendor before require.js itself and then jasmine/boot and helpers after require.js file.
Why do I think it's compromise? Becuase script contains anonymous define() shouldn't be loaded in page with require.js enabled, no matter it's loaded before or after require.js.
As long as you get started to use require.js, everything should be conveyed by require as AMD module or shim.
This is the rule that we have to follow in AMD world, simply loading script with anonymous define() before require.js isn't good practice. Everytime you meet this kind of issue, try to figure out in just mentioned method rather than loading it before require.js

[cloudchen]

Released v0.2.2 to address it.