Encore Versus Assetic?
Edit this pageWarning: You are browsing the documentation for Symfony 4.0, which is no longer maintained.
Read the updated version of this page for Symfony 6.2 (the current stable version).
Encore Versus Assetic?
Symfony originally shipped with support for Assetic: a pure PHP library capable of processing, combining and minifying CSS and JavaScript files. And while Encore is now the recommended way of processing your assets, Assetic still works well.
So what are the differences between Assetic and Encore?
| Assetic | Encore | |
| Language | Pure PHP, relies on other language tools for some tasks | Node.js |
| Combine assets? | Yes | Yes |
| Minify assets? | Yes (when configured) | Yes (out-of-the-box) |
| Process Sass/Less? | Yes | Yes |
| Loads JS Modules? [1]_ | No | Yes |
| Load CSS Deps in JS? [1] | No | Yes |
| React, Vue.js support? | No [2]_ | Yes |
| Support | Not actively maintained | Actively maintained |
- .. [1] JavaScript modules allow you to organize your JavaScript into small files
-
called modules and import them:
1 2 3 4 5
// require third-party modules var $ = require('jquery'); // require your own CoolComponent.js modules var coolComponent = require('./components/CoolComponent');Encore (via Webpack) parses these automatically and creates a JavaScript file that contains all needed dependencies. You can even require CSS or images.
- .. [2] Assetic has outdated support for React.js only. Encore ships with modern
- support for React.js, Vue.js, TypeScript, etc.
Should I Upgrade from Assetic to Encore
If you already have Assetic working in an application, and haven't needed any of the features that Encore offers over Assetic, continuing to use Assetic is fine. If you do start to need more features, then you might have a business case for changing to Encore.
