importmap-rails 0.6.1 → 0.6.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f7e0d50066c60a35a2490440f039b26f23a34426a5988ad5db9680cf3c436609
-  data.tar.gz: 630330c8ba8fa300c385d30449a69e8cf88b229a17f16b599b917a7258522bdb
+  metadata.gz: 66bfab7feb560eed6e33b6fddac090f10ffe0d66604257953083294c6fe1eb43
+  data.tar.gz: 1aebac7c0ac6d5e2d241c31804730bf986dd1d6a095a0b930afbdb132c9b77e3
 SHA512:
-  metadata.gz: 17082f8ca98917f7d046f62b4c5ed7efb68e72635025397afacdc5ed3fe5b4e048019e1f34e5348c435a609871b7069ae856731389a99687b8167e53ac16040a
-  data.tar.gz: 929d91e9ad8ae8d75201c08c7b72a56ce85d7774ac1eccfb44df9e22eb4dd3e7667626803ce5bd5c6278b20d0b100ad015534afdabc5ac872ed923da8482b010
+  metadata.gz: ad6c520f2677cb7b3322556258157c1abccc8bcacb21059803a7102bcd04ae1c047282febca97893b1f1b5cba4237d802ca1c2ea0b64b3cb09c3f26c6f7539af
+  data.tar.gz: ac70454957bfdb66c5316d3662f0cd44c5792676bea3f3c10b1ad2a85bb44d136cb15424729d8793350f5db515ed7706858c481c37718b71e4e7bd56507ce057

data/README.md

@@ -188,6 +188,9 @@ While import maps are native in Chrome and Edge, they need a shim in other brows
 
 Under certain circumstances, like running system tests using chromedriver under CI (which may be resource constrained and trigger errors in certain cases), you may want to explicitly turn off including the shim. If can do this by calling the bulk tag helper with `javascript_importmap_tags("application", shim: false)`. Thus you can pass in something like `shim: !ENV["CI"]`. If you want, and are sure you're not doing any full-page caching, you can also connect this directive to a user agent check (using a gem like `useragent`) to check whether the browser is chrome/edge 89+. But you really shouldn't have to, as the shim is designed to gracefully work with natively compatible drivers.
 
+## A note about browser extensions
+
+Certain extensions that also load Javascript modules may block import maps from being loaded (for instance, the Apollo Client Devtools extension). If you see a console message like `An import map is added after module script load was triggered`, browser extensions are likely the culprit. 
 
 ## License