1. Home
  2. Documentation
  3. Frontend
  4. Creating Page-Specific CSS/JS
WARNING: You are browsing the documentation for Symfony 4.0 which is not maintained anymore. Consider upgrading your projects to Symfony 5.1.

Creating Page-Specific CSS/JS

4.0 version
Maintained
3.4 4.4 5.1 current 5.0 5.2 master
Unmaintained
3.3 4.1 4.2 4.3

Creating Page-Specific CSS/JS

If you’re creating a single page app (SPA), then you probably only need to define one entry in webpack.config.js. But if you have multiple pages, you might want page-specific CSS and JavaScript.

For example, suppose you have a checkout page that has its own JavaScript. Create a new checkout entry:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
// webpack.config.js

Encore
    // an existing entry
    .addEntry('app', './assets/js/main.js')
    // a global styles entry
    .addStyleEntry('global', './assets/css/global.scss')

+     .addEntry('checkout', './assets/js/checkout.js')
;

Inside checkout.js, add or require the JavaScript and CSS you need. Then, just include a script tag for checkout.js on the checkout page (and a link tag for checkout.css if you import any CSS).

Multiple Entries Per Page?

Typically, you should include only one JavaScript entry per page. This means the checkout page will include checkout.js, but will not include the app.js that’s used on the other pages. Think of the checkout page as its own “app”, where checkout.js includes all the functionality you need.

However, if there is some global JavaScript that you want included on every page, you can create an entry that contains that code and include both that entry and your page-specific entry. For example, suppose that the app entry above contains JavaScript you want on every page. In that case, include both app.js and checkout.js on the checkout page.

Tip

Be sure to create a shared entry to avoid duplicating the Webpack bootstrap logic and any shared modules.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.