Any chance to support AssetMapper ?

[bernard-ng]

This bundle appears to be designed around a Webpack-based asset pipeline. With Symfony now promoting AssetMapper as a first-class alternative to Webpack, I wanted to ask about the project’s direction regarding asset management.

Is there any plan (or openness) to support AssetMapper, either as:

• a full alternative to Webpack integration, or
• an optional/secondary setup alongside the existing Webpack-based workflow?

If AssetMapper support is out of scope by design, a brief clarification in the documentation would also be helpful for users building new Symfony applications that aim to avoid Webpack entirely.

[nfacciolo]

Thanks for raising this — it’s a very valid point.

To be transparent, I hadn’t fully considered AssetMapper support yet. I did experiment with AssetMapper early on, but I consistently ran into dependency management issues, which made it difficult to use reliably in real-world projects. Because of that, I’ve continued to rely on Webpack by default in my projects, at least for now.

That said, I agree with you that AssetMapper is an important direction for Symfony, and it does seem intended to eventually replace Webpack for many use cases. Supporting AssetMapper — either as an alternative or an optional setup — definitely makes sense, especially for new Symfony applications that want to avoid Webpack entirely.

[nfacciolo]

I’ve added documentation about integrating the asset mapper in the README.md:
https://github.com/nfacciolo/base-ui?tab=readme-ov-file#alternative-using-assetmapper

I wasn’t able to test it myself, so I’m not sure if it works as expected.
Could you try it and let me know if you have any feedback or suggestions for improvement?