ResourceLoader/Developing with ResourceLoader

ResourceLoader supports complex client-side web applications in production and development environments. As these different environments have different needs, ResourceLoader offers two distinct modes: production mode and development (also known as "debug") mode.

Development mode is designed to make development as easy as possible, prioritizing the ease of identifying and resolving problems in the software over performance. Production mode makes the opposite prioritization, placing a premium value on performance at the cost of ease of development.

It is important to test your code in both development and production modes. In day-to-day development, most developers will find it beneficial to use development mode most of the time, only validating their code's functionality in production mode before committing changes.

Switching modes
As with many other of MediaWiki, ResourceLoader is configured to run in production mode by default. To have ResourceLoader operate in development mode by default, set the  variable to   in LocalSettings.php. For example:

""

Switching modes per-request
ResourceLoader requests, such as those made to load.php, contain a debug parameter in their query string. This parameter controls whether ResourceLoader runs in production or development mode for that particular request. This parameter may also be used with MediaWiki page requests, allowing the default mode set by  to be overridden.

To force ResourceLoader to operate in production mode for a particular request, append debug=false to the query string. For example: " http:// example.org/wiki/An_article?debug=false"

To force ResourceLoader to operate in development mode for a particular request, append debug=true to the query string. For example: " http:// example.org/w/index.php?title=An_article&action=edit&debug=true"

Breaking cache
When making frequent changes to code and checking them in a browser, the caching mechanisms designed to improve the performance of web-browsing can quickly become inconvenient. When developing on a system which is not making use of a reverse proxy such as Squid or Varnish, you only need to force your browser to bypass it's cache while refreshing. This can be achieved by pressing CTRL+F5 in Internet Explorer, or holding the shift key while clicking the browser's refresh button in most other browsers.

If you are developing behind a reverse proxy, you can either changed the values of $wgResourceLoaderMaxage or use ?debug=true to bypass cache since is fixed.