Replies: 1 comment · 4 replies
-
|
I would probably split this by entrypoints, not by As I understand it, I would do something like this: {# frontend layout #}
{{ importmap('frontend') }}
{# admin layout #}
{{ importmap('admin') }}Then each entrypoint can import its own bootstrap/controllers: // assets/frontend.js
import './frontend/bootstrap.js';
// assets/admin.js
import './admin/bootstrap.js';If both sides can use the normal Symfony UX loader, I would keep it. If the dependencies really conflict, I would make two small bootstrap files and register only the controllers needed for each side. So I would use |
Beta Was this translation helpful? Give feedback.
-
|
Hi @FmiKL, I have already 2 different js for importmap :
But if you want different things (configuration) on Symfony UX... I don't see. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, you're right, two entrypoints only solve the JS split. I had a similar need for separating frontend/admin code, so my first thought was to split the entrypoints too. If both So maybe the split cannot be fully done with Symfony UX config only, at least not just with two entrypoints. What I would try is to keep the normal Symfony UX setup for the controllers that can be shared, and for the part that really differs between front/admin, register those controllers manually in each bootstrap file. So something like: Symfony UX for the common part, and manual Stimulus registration only for the conflicting frontend/admin part. I don't know if there is a cleaner official way to have two different |
Beta Was this translation helpful? Give feedback.
-
|
I think we can play with this: https://symfony.com/bundles/StimulusBundle/current/index.html#configuration With Webpack it's possible, but with AssetMapper... |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I agree. With Webpack/Encore, you can point the bridge to a specific But with AssetMapper, I don't see an equivalent. It looks like So maybe this is the missing part for AssetMapper: being able to have named loaders/configs, like |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I like to manage differents stimulus controllers between my backend & frontend (cause conflicts between libs on backend/frontend, ex: different bootstrap, ...) and possible different Importmap.
We can have multiple paths: https://symfony.com/bundles/StimulusBundle/current/index.html#configuration bug not controllers.json?
What is the best way to manage this?
Beta Was this translation helpful? Give feedback.
All reactions