opal-zeitwerk 0.0.4 → 0.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c08d0237fce54d7885badfdda17e4c5b287627af98e41acb14f867ecc7b77631
-  data.tar.gz: 365a26b762cc3db8c2577bf093c87010a60315358f69572169a855f054bf7e71
+  metadata.gz: 846c4f821cd60dbcab5f85092d5fa8a74e1d507fa8c85e910931b2e26ac3b83c
+  data.tar.gz: 420eb1f0e0c4159c1631d606ddc190113d8b4ff5607605d67d554a824ecd2c12
 SHA512:
-  metadata.gz: c1cddfe4dfbfed3c28f8081e44d71cf3c4e6682d7d09ed3ca2f456251eb89b60c490fdaf192d9346c3c263655a1f2821a90791e42987c6693faebe151d503130
-  data.tar.gz: e89409525a50a0693ee2f8578020b618c44e2b33fe9561c02b1925c54b1c6c8e61505f80e03209b1244f5bd20c36b6049f514817139eaaa94f9238c5851aef99
+  metadata.gz: 974cea26a9f845c66cd540d57e06383e41c37d855ca07530f700d2d66ffd22297859bbe3a99a1fead00b2e8cb095048d62901d0b5ff8c406b50993b5cd3bfc38
+  data.tar.gz: e5c2140d6f15598c066368856da3e6d9b9e7cabea19d16fcfd3caef2fea6a9a88e4188dafa70b11484e0b5d4df790d6245c0c30d464be8c56fa1de5f79c2bc5a

data/README.md

@@ -51,7 +51,7 @@ Differences to Ruby Zeitwerk:
 - no logging (to keep asset size small and performance high)
 - no gem specific support: GemInflector, for_gem, etc.
 
-  These don't make so much sense, as Opal Zeitwerk works on the global Opal.modules registry in the Browser, not the filesystem. 
+  These don't make so much sense, as Opal Zeitwerk works on the global Opal.modules registry in the Browser, not the filesystem.
 - Zeitwerk::Loader.set_autoloads_in_dir is public, so it can be called from lazy loaded code, after updating Opal.modules.
 - There are no threads in javascript so thread support has been removed.
 - Tests don't run yet.
@@ -167,13 +167,9 @@ should define `Geolocatable`, not `Concerns::Geolocatable`.
 <a id="markdown-usage" name="usage"></a>
 ## Usage
 
-Currently autoloading requires the es6_modules_1_1 branch along with the Opal es6_modules compiler options enabled.
-This option is enabled by default with using [opal-webpack-loader](https://github.com/isomorfeus/opal-webpack-loader) to bundle opal code. 
-
 Add to the Gemfile:
 ```
-gem 'opal', github: 'janbiedermann/opal', branch: 'es6_modules_1_1' # required
-gem 'opal-webpack-loader', '~> 0.9.7' # required
+gem 'opal', '>= 1.3.0'
 gem 'opal-zeitwerk', '~> 0.0.1'
 ```
 
@@ -186,7 +182,7 @@ require 'zeitwerk'
 ### Setup
 Files must be included in the compiled asset by:
 ```
-require_tree 'some_dir', :autoload
+require_tree 'some_dir', autoload: true
 ```
 And added to the loader by:
 ```
@@ -451,10 +447,9 @@ As a workaround, you can eager load. Zeitwerk tries hard to succeed or fail cons
 <a id="markdown-supported-opal-versions" name="supported-opal-versions"></a>
 ## Supported Opal versions
 
-Opal Zeitwerk currently works only with the [Opal es6_modules_1_1 PR#1976](https://github.com/opal/opal/pull/1976) of Opal.
-For the Gemfile:
+Opal Zeitwerk currently works with Opal releases >= 1.3.0. For the Gemfile:
 ```
-gem 'opal', github: 'janbiedermann/opal', branch: 'es6_modules_1_1'
+gem 'opal', '>= 1.3.0'
 ```
 
 <a id="markdown-motivation" name="motivation"></a>

data/lib/opal/zeitwerk/version.rb

@@ -1,6 +1,6 @@
 # frozen_string_literal: true
 module Opal
   module Zeitwerk
-    VERSION = "0.0.4"
+    VERSION = "0.2.2"
   end
 end

data/opal/zeitwerk/loader/callbacks.rb

@@ -13,7 +13,7 @@ module Zeitwerk::Loader::Callbacks
 
     # "constant #{cpath(*cref)} loaded from file #{file}" if cdef?(*cref)
     if !cdef?(*cref)
-      raise Zeitwerk::NameError, "expected file #{file} to define constant #{cpath(*cref)}, but didn't"
+      raise Zeitwerk::NameError.new("expected file #{file} to define constant #{cpath(*cref)}, but didn't", cref.last)
     end
   end
 
@@ -25,11 +25,8 @@ module Zeitwerk::Loader::Callbacks
   # @return [void]
   def on_dir_autoloaded(dir)
     if cref = autoloads.delete(dir)
-      autovivified_module = if vivify_mod_dir && dir.start_with?(vivify_mod_dir)
-                              cref[0].const_set(cref[1], vivify_mod_class.new)
-                            else
-                              cref[0].const_set(cref[1], Module.new)
-                            end
+      autovivified_module = cref[0].const_set(cref[1], Module.new)
+
       # "module #{autovivified_module.name} autovivified from directory #{dir}"
 
       to_unload[autovivified_module.name] = [dir, cref] if reloading_enabled?