Mapear Activos

I've been using asset mapper while developing a small website and I encountered a problem when using it together with LiipImagineBundle to resize my images. When running in the dev environment, LiipImagineBundle can't find the images because of the additional hash that asset mapper adds to the file name.
My assets are in an assets directory in the project root.

<img src="{{ asset("img/my_image.png") | image_filter("fullhd") }}">

The generated path from asset mapper is assets/img/my_image-kNM.png . But because I am running in dev env, this "aliased" file does not really exist. LiipImagine however requires the file to exists in the file system and can't find it.

One way to fix this is by running asset-map:compile so the actual files exist in the public/assets directory. But I want to stay flexible while still developing and don't want to have to remember that I need to compile my asset map.

I modified the liip_imagine.yaml config and added the following lines so that Liip can find my assets and also stopped using the asset("...") twig function. I basically just let LiipImagine figure out where to load the images from.

    loaders:
        default:
            filesystem:
                data_root:
                    - '%kernel.project_dir%/public'
                    - '%kernel.project_dir%/assets'

Is there an easier way to use asset mapper together with LiipImagine? It feels like right now they are fighting with each other.

There is a problem with asset mapper in production enviroment with uploaded files since it requires the compile option to be run.

For example, if your app allows users to upload images, but they are private images, so you store them in assets, and then it works great when in dev, but in prod it doesnt work because compile is not being run after every image upload.

That makes asset mapper incompatible with uploaded images from vich uploader bundle, etc?

How can I include an image (e.g., an icon like assets/images/icon.png) in Symfony AssetMapper without applying versioning to it?

no more build system? :D mind is blown!

When running debug:asset it explodes!

  In JavaScriptImportPathCompiler.php line 119:

  Symfony\Component\AssetMapper\Compiler\JavaScriptImportPathCompiler::compile(): Return
  value must be of type string, null returned

It is likely to do with me experimenting with Symfony 7.

I can't find any info on it and am not sure right now if this is a showstopper.
I wonder if this rings any bell and if you have any super magic counterspell to this error.

Tnx!

Hi, nice to find that symfony goes back, abandoning once and for all the prebuilt js in favor of assets, among other things that of assets is a very old (not bad) concept used by an excellent framework (I won't name names) considered minor compared to symfony. Does this method promise to become the best way to deal with css and js or is it just an alternative? Thanks