rename AMD module definition to typeahead for requirejs compatability

[nikcub]

With the AMD module being defined as 'typeahead.js' requirejs configuration attempts to load the module from a relative file path since it assumes it is a file and not module reference.

For config to work with the module being loaded from the baseUrl require the .js extension to be removed from the AMD module definition.

Before:

requirejs.config({
  baseUrl: '/javascripts/',
  paths: {
    'typeahead.js': 'vendor/typeahead.js/dist/typeahead.jquery'
});

// Will attempt to load a file from ./typeahead.js 
require(['typeahead.js']);

renaming it doesn't work since the module is exported as typeahead.js

requirejs.config({
  baseUrl: '/javascripts/',
  paths: {
    'typeahead': 'vendor/typeahead.js/dist/typeahead.jquery'
});

// Won't load since the exported definition is typeahead.js 
require(['typeahead']);

Fixed version:

requirejs.config({
  baseUrl: '/javascripts/',
  paths: {
    'typeahead': 'vendor/typeahead/dist/typeahead.jquery'
});

// Loads
require(['typeahead']);

typeahead is already registered in bower so it will load correctly with nothing more than a definition name change

[nikcub]

Issues:

• RequireJS can't load typeahead.js module #1211
• hi, when I use requirejs and typeahead, it appear "Uncaught TypeError: undefined is not a function", it may be the method call problem, what can I do? #1271
• Bootstrap3-typeahead Issue 106

[nikcub]

I only just saw #1438

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}