[ImportMaps] Manage JavaScript dependencies without a JS toolchain #48371
+707
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Yarn, NPM, pnpm, Babel, SWC, Webpack, Rollup, Parcel... Is it really necessary to introduce so much complexity to create a beautiful and interactive website?
The Symfony UX initiative greatly simplified how to build frontend applications with Symfony by going back to the roots: server-side generated HTML (goodbye JSX, our good old Twig is back), and minimalist JavaScript thanks to Hotwire. However, to use Symfony UX, you still need to install, set up, and maintain a full JS toolchain... which is no picnic.
Is it still really necessary?! Browers recently gained features making it possible to do without most of them. Let's get rid of the complexity by using the web platform thanks to this new component!
The ImportMaps component is very similar to importmap-rails, but has command names similar to Composer.
Usage
Add or update packages:
Remove packages:
Update all packages to their latest versions:
Make the packages available in your app:
TODO