Skip to content

[Templates] Recommend Asset Mapper instead of Webpack #19880

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 15, 2024
Merged

[Templates] Recommend Asset Mapper instead of Webpack #19880

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions templates.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -329,8 +329,8 @@ as follows:
Build, Versioning & More Advanced CSS, JavaScript and Image Handling
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For help building, versioning and minifying your JavaScript and
CSS assets in a modern way, read about :doc:`Symfony's Webpack Encore </frontend>`.
For help building and versioning your JavaScript and
CSS assets in a modern way, read about :doc:`Symfony's AssetMapper </frontend>`.

.. _twig-app-variable:

Expand Down Expand Up @@ -1098,7 +1098,7 @@ JavaScript library.

First, include the `hinclude.js`_ library in your page
:ref:`linking to it <templates-link-to-assets>` from the template or adding it
to your application JavaScript :doc:`using Webpack Encore </frontend>`.
to your application JavaScript :doc:`using AssetMapper </frontend>`.

As the embedded content comes from another page (or controller for that matter),
Symfony uses a version of the standard ``render()`` function to configure
Expand Down