Read this guide if you'd like to know
Matomo uses the following JavaScript libraries:
Include new JS libraries only if they are vital to your plugin, and be sure to use the TypeScript workflow so there won't be clashes if a different version of the same library is used in other plugins. If many plugins decide to use a custom library, the UI will slow down.
Plugins can tell Matomo about to load JS and CSS asset files.
This is done through the AssetManager.getStylesheetFiles and AssetManager.getJavaScriptFiles events.
If you are new to events, check out our events guide. These events are defined in your plugin file (if your plugin name was YourPluginName then they would be defined in $matomoDir/plugins/YourPluginName/YourPluginName.php).
To load a file in the UI simply append the paths that should be loaded to the given $files array:
// these methods need to be in your plugin php file
public function registerEvents()
{
return array(
'AssetManager.getStylesheetFiles' => 'getStylesheetFiles',
'AssetManager.getJavaScriptFiles' => 'getJavaScriptFiles',
);
}
public function getStylesheetFiles(&$files)
{
$files[] = "plugins/MyPlugin/stylesheets/myStylesheet.less";
$files[] = "plugins/MyPlugin/stylesheets/myCssStylesheet.css";
}
public function getJavaScriptFiles(&$files)
{
$files[] = "plugins/MyPlugin/javascripts/myJavaScript.js";
}
In production environments, Matomo will concatenate all JavaScript files into one and minify it. LESS files will be compiled into CSS and merged into one CSS file. Matomo does not merge and minify JavaScript and CSS files on every request as it takes a long time to do this. They are only merged on certain events, such as when enabling a new plugin.
To make sure your changes will be actually visible and executed you need to enable the development mode in case you have not done yet:
./console development:enable
This way JavaScript files won't be merged and you can debug the original JavaScript source code.
Since version 4.5.0 it is possible to create components for the UI using Vue and TypeScript (though note that you do not have to use both; you can use Vue with ESnext (the most advanced version of EcmaScript) or just write plain TypeScript without using Vue).
Vue and TypeScript files are processed via webpack using the Vue CLI service, which is configured globally in Matomo. To take advantage of
this, create vue and vue/src subfolders in your plugin. Then add your code (TypeScript, ES, Vue) to the src subfolder. Make sure to
add an index.ts or index.js file to the subfolder and export everything you'd like to be programmatically accessible in the browser
(for example, by other plugins).
For an example of Vue code that works with Matomo, see the ExampleVue plugin source code.`
Once you've written your code, it must be built into a UMD file. Run the ./console vue:build MyPlugin command to build your
Vue/TypeScript code. The compiled UMD will be in the vue/dist folder, and should be distributed with the rest of your plugin
(since we do not expect all users to have access to node or the technical ability to compile our JavaScript manually).
While developing, it is recommended to use the --watch option with vue:build so you don't have to constantly re-run the
command.
Note: it is not necessary to add the resulting UMD file to the 'AssetManager.getJavaScriptFiles' event. Matomo will
automatically detect if one is there and use it (if the plugin is activated).
eslint
The Vue CLI is configured to run ESlint on files while building UMDs. If ESlint finds a style problem based on one of the
rules we configure, it will be printed out in the output of vue:build. Sometimes the actual problem or way to fix it
is not clear from the error message.
The easiest thing to do in this situation is to search for the rule name in a search engine. Each rule has associated documentation online that describes what the error means, why the rule exists and how to fix the error.
Eslint is automatically run when building Vue UMDs, but if you'd like to run it from the command line directly, run a command like:
$ npm run eslint -- --ext .js,.ts,.vue plugins/MyPlugin
Use of AngularJS is deprecated, please use Vue.js 3 instead.
The following is a list of special elements that you should be aware of as you develop your plugin or contribution:
#root: The root element of everything that is displayed and visible to the user.
#content: The root element that contains everything displayed under the main reporting menu and the row of 'selector' controls (ie, the period selector, the segment selector, etc.).
.top_controls: The element that contains the 'selector' controls. Only one of these elements.
.widgetContent: The root element of each widget. Events are posted to this specific element.
Matomo defines several global variables (held in window.piwik) regarding the current request. Here is what they are and how you should use them:
piwik.token_auth: The token_auth of the current user. Should be used in AJAX requests, but should never appear in the URL.piwik.piwik_url: The URL to this Matomo instance.piwik.userLogin: The current user's login handle (if there is a current user).piwik.idSite: The ID of the currently selected website.piwik.siteName: The name of the currently selected website.piwik.siteMainUrl: The URL of the currently selected website.piwik.language: The currently selected language's code (for example, en).When writing JavaScript for your contribution or plugin, you would ideally respect the following coding conventions.
Matomo Core defines many classes that should be reused by new plugins and contributions. These classes can be used to, among other things, change the page the UI shows, load a popover and get themed color values from CSS.
This class is considered deprecated and only exists for historical reasons as some components are still using it. Please use the MatomoUrl class instead..
The broadcast object is stored directly in the window object and has methods to parse the current URL.
broadcast contains several methods for parsing the Matomo URL. Matomo's main UI stores secondary set of query parameters in a URL's hash value. This is the URL that is loaded below the menu. broadcast's URL parsing functions will look for query parameter values in the hash as well as the main query string, so it is important to use them instead of directly accessing window.location.href.
broadcast provides the following functions:
isHashExists(): Returns the hash of the URL if it exists, false if otherwise.getHashFromUrl(): Returns the hash of the URL. Can be an empty string.getSearchFromUrl(): Returns the query string.extractKeyValuePairsFromQueryString(): Converts a query string to an object mapping query parameter names with query parameter values.getValuesFromUrl(): Returns an object mapping query parameter names with query parameter values for the current URL.getValueFromUrl(): Returns one query parameter value for the current URL by name.getValueFromHash(): Returns one query parameter value in the hash of the current URL by name.getHash(): Returns the hash of the URL.To learn more about an individual function, see the method documentation in the plugins/CoreHome/javascripts/broadcast.js file.
AJAX requests in non-Vue, Vanilla JavaScript should use the ajaxHelper global.
The ajaxHelper class should be used whenever you need to create an AJAX request. Plugins should not use $.ajax directly. ajaxHelper does some extra things that make it harder to write insecure code. It also keeps track of the current ongoing AJAX requests which is vital to the UI tests.
To use the ajaxHelper, create an instance, configure it, and then call the send() method. To learn more, read the documentation in the source code (located in plugins/Morpheus/javascripts/ajaxHelper.js).
For example:
(function ($) {
var ajaxHelper = window.ajaxHelper;
var ajax = new ajaxHelper();
ajax.setUrl('index.php?module=Actions&action=getPageUrls&idSite=1&date=today&period=day');
ajax.setCallback(function (response) {
$('#myReportContainer').html(response);
});
ajax.setFormat('html'); // the expected response format
ajax.setLoadingElement('#myReportContainerLoading');
ajax.send();
})(jQuery);
Below are some solutions to common problems that may occur during development:
vue:build --watch is running but the JavaScript isn't being built properly, try restarting the command. Internally it will
clear the webpack cache before watching again, which can solve some problems.npm test -- --clearCache command.