importmap-rails 1.0.1 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5fd79cf4031e5503a22e3013a53a35fb7ae5c3e11b1ace5791dd36429a6e5237
-  data.tar.gz: 3f993fba70aa37b5f80c4133c3e1a8aa64fc1b3d29096cf2d1bff823e5c9add5
+  metadata.gz: af8555e15d3527fb4cfa9fe96e9b23c62b19ad49071ea52d7791340ba8667266
+  data.tar.gz: 5ad2c59b8d549a5afd05505c5d957343db6eeb09947d21b69e96f0e483c5f0dc
 SHA512:
-  metadata.gz: cd7593f33ed2ff9c74b6c669f10a948cf2ee750ec136f269ff8d311c7851b7a3f2dbb81bb93c44ad505417a341c72169efdf6daf294f521a32179abdd4c2447f
-  data.tar.gz: 6e1f7fa74597f4407e03999433a20f1470fb2cb7cfa876b1d3e457cac14dffa08bdefe99110a42761ea736c13f356f50eeebfbaf5b4460d266fbd958ff99a837
+  metadata.gz: c743d9f4de29b6cda4b32fa866d3e8b30cfde1f68c1122fb0a29e4fa0fc33108e40a3d5deb4ebd7389268d952de78011df6367c5ed301bc621b7547ad8c19304
+  data.tar.gz: e640cf67cdc9fffc259619baede7a3b2c9f6d37c94bebb251d55a2b572500e045e3e16596ab7f5bd08e3915210ed96440c907ae644e21a3425c1f2ca385b658f

data/MIT-LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2021 Basecamp
+Copyright (c) 2022 Basecamp
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

data/README.md

@@ -1,8 +1,8 @@
 # Importmap for Rails
 
-[Import maps](https://github.com/WICG/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](https://world.hey.com/dhh/modern-web-apps-without-javascript-bundling-or-transpiling-a20f2755).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.
+[Import maps](https://github.com/WICG/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 ES modules (ESM) without the need for transpiling or bundling](https://world.hey.com/dhh/modern-web-apps-without-javascript-bundling-or-transpiling-a20f2755). 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.
+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 whole bundle, now only the cache for that single file is invalidated.
 
 There's [native support for import maps in Chrome/Edge 89+](https://caniuse.com/?search=importmap), and [a shim available](https://github.com/guybedford/es-module-shims) for any browser with basic ESM support. So your app will be able to work with all the evergreen browsers.
 
@@ -11,9 +11,8 @@ There's [native support for import maps in Chrome/Edge 89+](https://caniuse.com/
 
 Importmap for Rails is automatically included in Rails 7+ for new applications, but you can also install it manually in existing applications:
 
-1. Add `importmap-rails` to your Gemfile with `gem 'importmap-rails'`
-2. Run `./bin/bundle install`
-3. Run `./bin/rails importmap:install`
+1. Run `./bin/bundle add importmap-rails`
+2. Run `./bin/rails importmap:install`
 
 Note: In order to use JavaScript from Rails frameworks like Action Cable, Action Text, and Active Storage, you must be running Rails 7.0+. This was the first version that shipped with ESM compatible builds of these libraries.
 
@@ -42,7 +41,7 @@ to 1 of the 3 viable ways of loading ES Module javascript packages.
 For example:
 
 ```rb
-# config/importmaps.rb
+# config/importmap.rb
 pin "react", to: "https://ga.jspm.io/npm:react@17.0.2/index.js"
 ```
 
@@ -224,6 +223,41 @@ pin_all_from File.expand_path("../app/assets/javascripts", __dir__)
 ```
 
 
+## Selectively importing modules
+
+You can selectively import your javascript modules on specific pages.
+
+Create your javascript in `app/javascript`:
+
+```js
+// /app/javascript/checkout.js
+// some checkout specific js
+```
+
+Pin your js file:
+
+```rb
+# config/importmap.rb
+# ... other pins...
+pin "checkout"
+```
+
+Import your module on the specific page. Note: you'll likely want to use a `content_for` block on the specifc page/partial, then yield it in your layout.
+
+```erb
+<% content_for :head do %>
+  <%= javascript_import_module_tag "checkout" %>
+<% end %>
+```
+
+**Important**: The `javascript_import_module_tag` should come after your `javascript_importmap_tags`
+
+```erb
+<%= javascript_importmap_tags %>
+<%= yield(:head) %>
+```
+
+
 ## Include a digest of the import map in your ETag
 
 If you're using [ETags](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag) generated by Rails helpers like `stale?` or `fresh_when`, you need to include the digest of the import map into this calculation. Otherwise your application will return 302 cache responses even when your JavaScript assets have changed. You can avoid this with something like: