jsg 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f1d60a874b6a2f773a473b333c5f2ff4db6d47f532dc1a257c1c1c34b7a226f8
-  data.tar.gz: 5f777d0b59c0454922d48bdf9b2a03b09b62ba106a7fb952d368276579cd6ade
+  metadata.gz: c5bbe669419df7b6181dacae7851ccf5a27b97abdf6e6a4a2a48c73e10d87632
+  data.tar.gz: c838fccba5ca6a8316d0718b097312b3760f31b94f9112eeee1bf1e7053c142f
 SHA512:
-  metadata.gz: f4100bdf2b90ebe3c9a930e5981dcc99da12efd458602021d41631b9f61056ad6986ca1e93bc26f639e43977beebc2b73b7fe95f6d7a993b9f221a141fc015d8
-  data.tar.gz: f80229f22ac0201a35ba6582a1de2a50692ac118da9dc100df638df85f13517fdf2a00396bce4ada9ae32f8c502c8a6a38d1e5f1f4d3cb7b9cff1ae0feb339f1
+  metadata.gz: 448f59e03a1e7a38c89f0ff99e5ff32ddda31fd3009bef7d712929ce93c4b7804aba3d137df8c4aff25f051f47a4bec023ad211a907da1ed06c2de4baa53c850
+  data.tar.gz: 5bfbcff342b82afd36fd558eb8a63052f8b2699e98f5d65eebdb5c5c2cb0dd67dbab2c9505fd28227ed6d2716e32070dce6aded230627ec8bbc37e0786d9fe82

data/CHANGELOG.md

@@ -1,5 +1,15 @@
 ## [Unreleased]
 
+## [0.3.0] - 2026-11-05
+
+- New opt-in `require "jsg/global"`: unknown methods on the `JS` module are forwarded to `JS.global`, so `JS.document.title`, `JS.alert("Hi")` and `JS.myValue = 1` work. Names the `JS` module already answers keep their meaning (`JS.global`, `JS.eval`, and Ruby's own module methods such as `JS.name`). It loads `jsg` too. `require "jsg"` alone does not change the `JS` module.
+- The ruby.wasm tests run every test file in a fresh VM, so a file that only requires `jsg/global` is tested on its own.
+
+## [0.2.1] - 2026-09-29
+
+- First release published from GitHub Actions with RubyGems trusted publishing (`.github/workflows/release.yml`, triggered by `v*` tags).
+- CI runs the ruby.wasm tests on Node.js 24. Node 22's WASI crashes once Ruby loads files from a mounted directory.
+
 ## [0.2.0] - 2026-09-29
 
 - Fix `require "jsg"`: the library moved from the gem root to `lib/jsg.rb`, so it is on the load path.

data/README.md

@@ -97,6 +97,29 @@ el.tap { |e| ... } # like Kernel#tap (JS::Object is a BasicObject since js 2.10)
 value == true     # comparing with true, false and nil works (JavaScript's == rules)
 ```
 
+### `JS.document` instead of `JS.global.document` (opt-in)
+
+`require "jsg/global"` forwards unknown methods on the `JS` module to `JS.global`. It loads `jsg` as well, so this one line is enough:
+
+```ruby
+require "jsg/global"
+
+JS.document.title             # JS.global.document.title
+JS.alert("Hello")             # JS.global.alert("Hello")
+JS.localStorage.getItem("k")
+JS.myValue = 1                # sets window.myValue
+JS.hidden?                    # JavaScript truthiness, like the ? methods above
+```
+
+It is not part of `require "jsg"` because it changes the `JS` module itself, which the js gem and other libraries use too. Load it when you want the shorter syntax in your own app.
+
+Only names that `JS` does not already answer are forwarded. These keep their Ruby meaning, so use `JS.global` for a browser global of the same name:
+
+- methods of the js gem: `JS.global`, `JS.eval`, `JS.try_convert`, `JS.is_a?`, ...
+- methods every Ruby module has: `JS.name` (returns `"JS"`, not `window.name`), `JS.hash`, `JS.inspect`, `JS.class`, `JS.method`, `JS.display`, `JS.freeze`, ...
+
+Private `Kernel` methods such as `open`, `print` or `format` are forwarded, because calling them with an explicit receiver (`JS.open(...)`) ends up in `method_missing`. A name that the global object does not have raises `NoMethodError` as before. `JSG.xxx` forwards to `JS`, so after `require "jsg/global"` it reaches the globals too.
+
 ## Development
 
 ```bash
@@ -104,7 +127,16 @@ bin/setup
 bundle exec rake    # rspec, the ruby.wasm tests and rubocop
 ```
 
-The specs in `spec/` test the command line tool on your normal Ruby. `lib/jsg.rb` needs the js gem, which only works inside ruby.wasm, so its tests in `test/wasm` run the prebuilt ruby.wasm on Node.js (`bundle exec rake test:wasm`, needs Node.js and npm).
+To release a new version, update `lib/jsg/version.rb` and `CHANGELOG.md`, commit, and push a matching tag:
+
+```bash
+git tag v0.3.0
+git push origin v0.3.0
+```
+
+The `Release` workflow runs the tests and publishes the gem to RubyGems.org with trusted publishing, so no API key is stored in GitHub.
+
+The specs in `spec/` test the command line tool on your normal Ruby. `lib/jsg.rb` needs the js gem, which only works inside ruby.wasm, so its tests in `test/wasm` run the prebuilt ruby.wasm on Node.js (`bundle exec rake test:wasm`, needs Node.js 24 or newer and npm).
 
 ## License
 

data/lib/jsg/global.rb

@@ -0,0 +1,46 @@
+# frozen_string_literal: true
+
+require "jsg"
+
+module JSG
+  # Opt-in shortcut: forwards unknown methods on the JS module to JS.global,
+  # so browser globals can be used without writing JS.global every time.
+  #
+  #   require "jsg/global"
+  #
+  #   JS.document.title           # JS.global.document.title
+  #   JS.alert("Hello")           # JS.global.alert("Hello")
+  #   JS.localStorage.getItem("k")
+  #   JS.myValue = 1              # sets window.myValue
+  #
+  # It is a separate file because it changes the JS module itself, which the
+  # js gem and other libraries also use. `require "jsg"` alone does not load it.
+  #
+  # Only names that JS does not already answer are forwarded. These keep their
+  # Ruby meaning, so use JS.global for the browser global of the same name:
+  #
+  # - methods of the js gem: JS.global, JS.eval, JS.try_convert, JS.is_a?, ...
+  # - methods every Ruby module has: JS.name (returns "JS", not window.name),
+  #   JS.hash, JS.inspect, JS.class, JS.method, JS.display, JS.freeze, ...
+  #
+  # Private Kernel methods such as open, print or format are forwarded, because
+  # calling them with an explicit receiver (JS.open) ends up in method_missing.
+  # A name the global object does not have raises NoMethodError as usual.
+  module Global
+    # Sends +name+ with its arguments and block to JS.global if the global
+    # object responds to it (property read, setter, method call or predicate,
+    # as handled by the jsg patch); otherwise raises NoMethodError via super.
+    def method_missing(name, ...)
+      return super unless global.respond_to?(name)
+
+      global.__send__(name, ...)
+    end
+
+    # Makes JS.respond_to?(name) true for the names method_missing forwards.
+    def respond_to_missing?(name, include_private = false)
+      global.respond_to?(name) || super
+    end
+  end
+end
+
+JS.extend(JSG::Global)

data/lib/jsg/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module JSG
-  VERSION = "0.2.0"
+  VERSION = "0.3.0"
 end

data/sig/jsg.rbs

@@ -1,4 +1,9 @@
 module JSG
   VERSION: String
-  # See the writing guide of rbs: https://github.com/ruby/rbs#guides
+
+  # require "jsg/global": forwards unknown methods on the JS module to JS.global
+  module Global
+    def method_missing: (Symbol name, *untyped args) ?{ (*untyped) -> untyped } -> untyped
+    def respond_to_missing?: (Symbol name, ?bool include_private) -> bool
+  end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: jsg
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.0
 platform: ruby
 authors:
 - Andi
@@ -53,6 +53,7 @@ files:
 - exe/jsg
 - lib/jsg.rb
 - lib/jsg/cli.rb
+- lib/jsg/global.rb
 - lib/jsg/version.rb
 - sig/jsg.rbs
 - template/Gemfile
@@ -81,7 +82,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.18
+rubygems_version: 4.0.20
 specification_version: 4
 summary: JSG helps setting up ruby.wasm projects and comes with a nicer syntax
 test_files: []