Cowboys Kicker Brandon Aubrey Sets NFL Records on TNF vs. Lions
- This is a configuration file, likely for a JavaScript module loader like RequireJS.Let's break down what it contains:
- This section defines the mapping between logical module names (used in require() calls in your JavaScript code) and the actual file paths where those modules are located.
- * Top-Level paths: This is the main mapping.For example: * ".custom": "2.6.2": Means that when your code does require(".custom"), the loader will look for a file at...
This is a configuration file, likely for a JavaScript module loader like RequireJS.Let’s break down what it contains:
1. paths:
This section defines the mapping between logical module names (used in require() calls in your JavaScript code) and the actual file paths where those modules are located. It’s organized into nested objects.
* Top-Level paths: This is the main mapping.For example:
* ".custom": "2.6.2": Means that when your code does require(".custom"), the loader will look for a file at 2.6.2 (presumably a relative path, or a path defined elsewhere).
* "libs/velocity": "1.2.2": require("libs/velocity") will load the file at 1.2.2.
* "libs/jquery/ui/jquery.ui.datepicker": "1.11.4": require("libs/jquery/ui/jquery.ui.datepicker") will load the file at 1.11.4.
* libs: A large portion of the paths are nested under libs, indicating these are third-party libraries. This is a common practice to organize dependencies. You see a lot of jQuery UI components here, along with DataTables, Velocity.js, and other utilities.
* fly: Another nested section, likely representing modules specific to a project or framework named “fly”.
2. shim:
The shim configuration is crucial for loading modules that don’t follow the standard asynchronous module definition (AMD) format that RequireJS expects. These are typically older JavaScript libraries that were written before AMD became popular.shim tells RequireJS how to load these modules and their dependencies.
* liveconnection/managers/connection: This module depends on liveconnection/libs/sockjs-0.3.4. The deps array lists the dependencies.
* liveconnection/libs/sockjs-0.3.4: This module exports a global variable named SockJS. The exports property tells RequireJS to make sockjs available as a module.
* libs/setValueFromArray and libs/getValueFromArray: These modules also export global variables (set and get respectively).
* fly/libs/backbone.marionette: This module depends on jQuery, Underscore.js, and Backbone.js. It also exports Marionette.
* fly/libs/underscore-1.5.1 and fly/libs/backbone-1.0.0: These modules export global variables _ and Backbone respectively.
* libs/jquery/ui/jquery.ui.tabs-1.11.4: This module depends on jQuery, the core jQuery UI components, and a utility module fly/libs/jquery.widget.
* libs/jquery/flexslider-2.1: Depends on jQuery.
* libs/dataTables.fixedColumns-3.0.4 and libs/dataTables.fixedHeader-2.1.2: Depend on jQuery and DataTables.
* https://sports.cbsimg.net/js/CBSi/app/VideoPlayer/AdobePass-min.js: Depends on a utility script from the same domain.
3. map:
The map configuration allows you to define aliases or remaps for modules. This is useful for handling different versions of libraries or for providing more convenient names.
* *: the asterisk means these mappings apply globally to all modules.
* adobe-pass: Maps the logical name adobe-pass to the URL https://sports.cbsimg.net/js/CBSi/app/VideoPlayer/AdobePass-min.js.
* facebook and facebook-debug: Maps