summaryrefslogtreecommitdiff
path: root/www/rubygem-importmap-rails-rails80/pkg-descr
diff options
context:
space:
mode:
Diffstat (limited to 'www/rubygem-importmap-rails-rails80/pkg-descr')
-rw-r--r--www/rubygem-importmap-rails-rails80/pkg-descr17
1 files changed, 17 insertions, 0 deletions
diff --git a/www/rubygem-importmap-rails-rails80/pkg-descr b/www/rubygem-importmap-rails-rails80/pkg-descr
new file mode 100644
index 000000000000..184d7013fa42
--- /dev/null
+++ b/www/rubygem-importmap-rails-rails80/pkg-descr
@@ -0,0 +1,17 @@
+Import maps let you import JavaScript modules using logical names that map to
+versioned/digested files -- directly from the browser. So you can build modern
+JavaScript applications using JavaScript libraries made for ESM without the need
+for transpiling or bundling.This frees you from needing Webpack, Yarn, npm, or
+any other part of the JavaScript toolchain. All you need is the asset pipeline
+that's already included in Rails.
+
+With this approach you'll ship many small JavaScript files instead of one big
+JavaScript file. Thanks to HTTP/2 that no longer carries a material performance
+penalty during the initial transport, and in fact offers substantial benefits
+over the long run due to better caching dynamics. Whereas before any change to
+any JavaScript file included in your big bundle would invalidate the cache for
+the the whole bundle, now only the cache for that single file is invalidated.
+
+There's native support for import maps in Chrome/Edge 89+, and a shim available
+for any browser with basic ESM support. So your app will be able to work with
+all the evergreen browsers.