Add custom Javascript

Overview
If you want to add interactivity to your storefront you probably have to write your own JavaScript plugin. Here you will be guided through the process of writing and registering your own JavaScript plugins. You will write a plugin that simply checks if the user has scrolled to the bottom of the page and then creates an alert.
Prerequisites
You need for this guide a running plugin and therefore a running Shopware 6 instance, with full access to all files. This also includes access to the command line to execute a command, which then builds the storefront. A general understanding of vanilla JavaScript ES6 is also mandatory. Everything else is explained in this guide itself.
Writing a JavaScript plugin
Storefront JavaScript plugins are vanilla JavaScript ES6 classes that extend from our Plugin base class. For more background information on JavaScript classes, take a look here.
The directory to create custom javascript plugins should be the following, which represents the same structure like the core: <plugin root>/src/Resources/app/storefront/src/
In there, you create a new directory, named after your plugin. In this guide, this will be called example-plugin, so the full path would look like this: <plugin root>/src/Resources/app/storefront/src/example-plugin
Now create an actual file for your JavaScript plugin, in this example it will be called example-plugin.plugin.js.
Inside this file create and export an ExamplePlugin class that extends the base Plugin class:
<plugin root>/src/Resources/app/storefront/src/example-plugin/example-plugin.plugin.js
1
import Plugin from 'src/plugin-system/plugin.class';
2
​
3
export default class ExamplePlugin extends Plugin {
4
}
Copied!
This is just a basic vanilla JavaScript ES6 class, which extends the Plugin class.
Each plugin has to implement the init() method. This method will be called when your plugin gets initialized and is the entrypoint to your custom logic. The plugin initialization runs on DOMContentLoaded event, so you can be sure, that the dom is already completely loaded. In your case you add a callback to the scroll event from the window and check if the user has scrolled to the bottom of the page. If so we display an alert. Your full plugin now looks like this:
<plugin root>/src/Resources/app/storefront/src/example-plugin/example-plugin.plugin.js
1
import Plugin from 'src/plugin-system/plugin.class';
2
​
3
export default class ExamplePlugin extends Plugin {
4
    init() {
5
        window.addEventListener('scroll', this.onScroll.bind(this));
6
    }
7
​
8
    onScroll() {
9
        if ((window.innerHeight + window.pageYOffset) >= document.body.offsetHeight) {
10
            alert('Seems like there\'s nothing more to see here.');
11
        }
12
    }
13
}
Copied!
A short explanation what the condition is doing here: The window.innerHeight contains the height of the window, as you might have guessed.
This is added to window.pageYOffset, which contains the current scroll position on the Y-axis. It represents the top value of the current scroll, which basically means: If your website is 5000px high and you scroll to the very bottom, the value would not be 5000px, but rather 5000px - window.innerHeight. Thus, we have to add up the innerHeight to actually get the bottom of the website.
Well, and then we check if this sum is bigger or equal the total size of your website, by fetching the height of your website's body tag. If it is higher or equal the total height of the website, you reached the end of the website.
Registering your plugin
Next you have to tell Shopware that your plugin should be loaded and executed. Therefore you have to register your plugin in the PluginManager.
Shopware is automatically looking for a main.js file in a directory <plugin root>/src/Resources/app/storefront/src, which then will be loaded automatically. Consider this to be your main storefront JavaScript entrypoint.
Create a main.js file inside your <plugin root>/src/Resources/app/storefront/src folder and get the PluginManager from the global window object. Then register your own plugin:
<plugin root>/src/Resources/app/storefront/src/main.js
1
// Import all necessary Storefront plugins
2
import ExamplePlugin from './example-plugin/example-plugin.plugin';
3
​
4
// Register your plugin via the existing PluginManager
5
const PluginManager = window.PluginManager;
6
PluginManager.register('ExamplePlugin', ExamplePlugin);
Copied!
Right now, your plugin will automatically be loaded once you load the website.
Binding your plugin to the DOM
You can also bind your plugin to a DOM element by providing a css selector:
<plugin root>/src/Resources/app/storefront/src/main.js
1
 // Import all necessary Storefront plugins
2
 import ExamplePlugin from './example-plugin/example-plugin.plugin';
3
​
4
 // Register your plugin via the existing PluginManager
5
 const PluginManager = window.PluginManager;
6
 PluginManager.register('ExamplePlugin', ExamplePlugin, '[data-example-plugin]');
Copied!
In this case the plugin just gets executed if the HTML document contains at least one element with the data-example-plugin attribute. You can then use this.el inside your plugin to access the DOM element your plugin is bound to.
Loading your plugin
The following will create a new template with a very short explanation. If you're looking for more information on what's going on here, head over to our guide about Customizing templates.
You bound your plugin to the css selector [data-example-plugin], so you have to add DOM elements with this attribute on the pages you want your plugin to be active.
Create a <plugin root>/src/Resources/views/storefront/page/content/ folder and create a index.html.twig template. Inside this template, extend from the @Storefront/storefront/page/content/index.html.twig and overwrite the base_main_inner block. After the parent content of the blog, add a template tag that has the data-example-plugin attribute.
A lot of text, here is the respective example:
<plugin root>/src/Resources/views/storefront/page/content/index.html.twig
1
​
Copied!
1
<div data-gb-custom-block data-tag="sw_extends" data-0='@Storefront/storefront/page/content/index.html.twig'>
2
​
3
<div data-gb-custom-block data-tag="block">
4
​
5
    {{ parent() }}
6
​
7
    <template data-example-plugin></template>
8
​
9
</div>
Copied!
With this template extension your plugin is active on every content page, like the homepage or category listing pages.
Configuring your plugins
You can configure your plugins from inside the templates via data-options. First you have to define a static options object inside your plugin and assign your options with default values to it. In your case define a text option and as a default value use the text you previously directly prompted to the user. And instead of the hard coded string inside the alert(), use your new option value.
<plugin root>/src/Resources/app/storefront/src/example-plugin/example-plugin.plugin.js
1
import Plugin from 'src/plugin-system/plugin.class';
2
​
3
export default class ExamplePlugin extends Plugin {
4
    static options = {
5
        /**
6
         * Specifies the text that is prompted to the user
7
         * @type string
8
         */
9
        text: 'Seems like there\'s nothing more to see here.',
10
    };
11
​
12
    init() {
13
        window.addEventListener('scroll', this.onScroll.bind(this));
14
    }
15
​
16
    onScroll() {
17
        if ((window.innerHeight + window.pageYOffset) >= document.body.offsetHeight) {
18
            alert(this.options.text);
19
        }
20
    }
21
}
Copied!
Now you are able to override the text that is prompted to the user from inside your templates. For this example we're going to display another message on product detail pages.
Therefore create a product-detail folder inside your <plugin root>/src/Resources/views/storefront/page folder and add an index.html.twig file inside that folder. In your template extend from the default @Storefront/storefront/page/product-detail/index.html.twig and override the block page_product_detail_content.
After the parent content add a template tag with the data-example-plugin tag to activate your plugin on product detail pages as well. Next add a data-{your-plugin-name-in-kebab-case}-options (in this example: data-example-plugin-options) attribute to the DOM element you registered your plugin on (the template tag). The value of this attribute are the options you want to override as a JSON object.
<plugin root>/src/Resources/views/storefront/page/product-detail/index.html.twig
1
​
Copied!
1
<div data-gb-custom-block data-tag="sw_extends" data-0='@Storefront/storefront/page/product-detail/index.html.twig'>
2
​
3
{% set examplePluginOptions = {
4
    text: "Are you not interested in this product?"
5
} %}
6
​
7
<div data-gb-custom-block data-tag="block">
8
​
9
    {{ parent() }}
10
​
11
    <template data-example-plugin data-example-plugin-options='{{ examplePluginOptions|json_encode }}'></template>
12
​
13
</div>
Copied!
It is best practice to use a variable for the options because this is extendable from plugins.
Modify existing options
We've just mentioned the best practice to use a template variable for setting plugin options, so other plugins can extend those options. This section will explain how to do actually achieve that.
You can use the replace_recursive Twig filter for this case.
Imagine the following example can be found in the core:
1
{% set productSliderOptions = {
2
    productboxMinWidth: sliderConfig.elMinWidth.value ? sliderConfig.elMinWidth.value : '',
3
    slider: {
4
        gutter: 30,
5
        autoplayButtonOutput: false,
6
        nav: false,
7
        mouseDrag: false,
8
        controls: sliderConfig.navigation.value ? true : false,
9
        autoplay: sliderConfig.rotate.value ? true : false
10
    }
11
} %}
12
​
13
<div data-gb-custom-block data-tag="block">
14
​
15
    <div class="base-slider"
16
         data-product-slider="true"
17
         data-product-slider-options="{{ productSliderOptions|default({})|json_encode|escape('html_attr') }}">
18
    </div>
19
​
20
</div>
Copied!
Now you want to overwrite the value slider.mouseDrag with your plugin. The variable can be overwritten with replace_recursive:
1
<div data-gb-custom-block data-tag="block">
2
​
3
    {% set productSliderOptions = productSliderOptions|replace_recursive({
4
        slider: {
5
            mouseDrag: true
6
        }
7
    }) %}
8
​
9
    {{ parent() }}
10
​
11
</div>
Copied!
Plugin script path
For JavaScript you normally would have two locations where your *.js files are located. You have your main.js as an entry point inside of the following directory: <plugin root>/src/Resources/app/storefront/src.
Shopware will then compile the JavaScript and save the compiled version at <plugin root>/src/Resources/app/storefront/dist/storefront/js/<plugin-name>.js. This file will be recognized automatically by Shopware.
Make sure to ship the compiled file with your plugin as well.
Testing your changes
To see your changes you have to build the storefront. Use the following command and reload your storefront:
Development template
Production template
1
./psh.phar storefront:build
Copied!
1
./bin/build-storefront.sh
Copied!
If you now scroll to the bottom of your page an alert should appear.
Next steps
You've got your own first javascript plugin running. You might want to start listening to javascript events now, or even override other javascript plugins instead.
Add dynamic content via AJAX calls
Override existing Javascript
Last modified 1mo ago
Copy link
Edit on GitHub
Contents
Overview
Prerequisites
Writing a JavaScript plugin
Registering your plugin
Binding your plugin to the DOM
Loading your plugin
Configuring your plugins
Modify existing options
Plugin script path
Testing your changes
Next steps