[LiveComponent] Separation of concerns #2909
Replies: 6 comments
-
This is more a "StimulusBundle + Webpack" thing (i mean it's the case for all the UX packages) .. except if you use AssetMapper :) More information about the process here: https://symfony.com/bundles/StimulusBundle/current/index.html#how-are-the-stimulus-controllers-loaded You will probably find some ideas to do it manually (but you will need composer install at one time to fetch the assets) |
Beta Was this translation helpful? Give feedback.
-
Thank you for this issue. |
Beta Was this translation helpful? Give feedback.
-
It has been clarified but not resolved |
Beta Was this translation helpful? Give feedback.
-
Thank you for this issue. |
Beta Was this translation helpful? Give feedback.
-
Could I get an answer? If I do not hear anything I will assume this issue is resolved or abandoned. Please get back to me <3 |
Beta Was this translation helpful? Give feedback.
-
NPM packages have been introduced in 2.24.0, see https://www.npmjs.com/search?q=%40symfony%2Fux- |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
After being introduced to the live-components there is one thing that struck me. When installing the package I have an entry in my
package.json
containing;"@symfony/ux-live-component": "file:vendor/symfony/ux-live-component/assets",
Now when running my builds I need both Yarn and Composer on my front-end containers which increases the software dependencies and build times. It also requires more maintenance to keep this extra package version in line.
I couldn't find this package on npmjs.com, which made me wonder. Am I using this wrong? Is this as designed? Or could this be improved?
Beta Was this translation helpful? Give feedback.
All reactions