opal 1.3.0 → 1.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0b7a4b076832e2c4f5cf807f40bf1a9d7e1a0328e1ef4b245f1514ae2ff145dd
-  data.tar.gz: 5df94eda8d910641c918d913b7421796b5e513b05600e51d1debd0cd3944cf20
+  metadata.gz: ec2d9bb3f02059898f9a494c018fbcb4f451c4c5130b3e9ff455bf3ce1561fc9
+  data.tar.gz: a69e0554d43a0ef0ad6e7d439beb313536227615698487b8283321e879cf150d
 SHA512:
-  metadata.gz: 04050f1589cf7ee4a3be39907e4618434659157968b63f225c6ae27a46da5f9e77c57080ca0c741aa333c3a3e48e2bbe38a3719f8540e55aefe26a3b6c4d3710
-  data.tar.gz: 867a69aa3810572ff1636f4b6dc0df14435fa54dc06655101dde8017e71ab1892393e5a61517194f4828d596301097876e36734d9c4039f2d2109c70a011a3cb
+  metadata.gz: 5a96aade4e8183b8f00136eb4c5e64ea1f6b12b03aec98096476de4dd414b03b9ecfb90658a29bef403b366e36db43283b6e175cac5dcc3796453535f9ad7bd0
+  data.tar.gz: 8ea23169b1492a34b5bf98750259f9d9da636bb5070b50fad624a56a2eea65f4c5975a6385af3dfbdfad2a41985f5d32ba3aa583feea39b79b59ccc3cac20c43

data/.eslintrc.js

@@ -30,5 +30,6 @@ module.exports = {
     "globalThis": "readonly",
     "Uint8Array": "readonly",
     "Promise": "readonly",
+    "WeakRef": "readonly",
   }
 };

data/.github/workflows/build.yml

@@ -71,9 +71,6 @@ jobs:
         uses: ruby/setup-ruby@v1
         with:
           ruby-version: ${{ matrix.combo.ruby }}
-          # NOTE: Bundler 2.2.0 fails to install libv8
-          # https://github.com/rubyjs/libv8/issues/310
-          bundler: "2.1.4"
           bundler-cache: false
       - run: ruby bin/git-submodule-fast-install
       - run: bundle lock

data/.rubocop.yml

@@ -2,7 +2,7 @@ require: rubocop-performance
 inherit_from: .rubocop/todo.yml
 
 AllCops:
-  TargetRubyVersion: 2.5
+  TargetRubyVersion: 2.6
   Exclude:
     - CHANGELOG.md
     - CONDUCT.md
@@ -52,6 +52,10 @@ AllCops:
     - 'stdlib/matrix/*.rb'
     - 'stdlib/pp.rb'
     - 'stdlib/prettyprint.rb'
+    - 'stdlib/optparse.rb'
+    - 'stdlib/optparse/*.rb'
+    - 'stdlib/tmpdir.rb'
+    - 'stdlib/tempfile.rb'
 
 inherit_mode:
   merge:

data/CHANGELOG.md

@@ -15,6 +15,111 @@ Changes are grouped as follows:
 
 
 
+## [1.4.0](https://github.com/opal/opal/compare/v1.3.2...v1.4.0) - 2021-12-24
+
+
+### Added
+
+- Implement `chomp:` option for `String#each_line` and `#lines` ([#2355](https://github.com/opal/opal/pull/2355))
+- Ruby 3.1 support and some older Ruby features we missed ([#2347](https://github.com/opal/opal/pull/2347))
+  - Use parser in 3.1 mode to support new language-level features like hashes/kwargs value omission, the pin operator for pattern matching
+  - `Array#intersect?`
+  - `String#strip` and `String#lstrip` to also remove NUL bytes
+  - `Integer.try_convert`
+  - `public`, `private`, `protected`, `module_function` now return their arguments
+  - `Class#descendants`, `Class#subclasses`
+  - (<=1.8) `Kernel#local_variables`
+  - (<=2.3) Set local variables for regexp named captures (`/(?<b>a)/ =~ 'a'` => `b = 'a'`)
+  - Remove deprecated `NIL`, `TRUE`, `FALSE` constants
+  - `String#unpack` and `String#unpack1` to support an `offset:` kwarg
+  - `MatchData#match`, `MatchData#match_length`
+  - Enumerable modernization
+    - `Enumerable#tally` to support an optional hash accumulator
+    - `Enumerable#each_{cons,slice}` to return self
+    - `Enumerable#compact`
+  - `Refinement` becomes its own class now
+  - `Struct#keyword_init?`
+  - (pre-3.1) Large Enumerator rework
+    - Introduce `Enumerator::ArithmeticSequence`
+    - Introduce `Enumerator::Chain`
+    - Introduce `Enumerator#+` to create `Enumerator::Chain`s
+    - `Enumerator#{rewind,peek,peek_values,next,next_values}`
+    - Improve corelib support for beginless/endless ranges and `ArithmeticSequences`
+      - `String#[]`, `Array#[]`, `Array#[]=`, `Array#fill`, `Array#values_at`
+    - `Range#step` and `Numeric#step` return an `ArithmeticSequence` when `Numeric` values are in play
+    - Introduce `Range#%`
+    - `Enumerator::Yielder#to_proc`
+    - Fix #2367
+  - (2.7) `UnboundMethod#bind_call`
+  - (Opal) `{Kernel,BasicObject}#{inspect,p,pp,method_missing}` may work with JS native values now, also they now correctly report cycles
+  - `Enumerable#sum` uses Kahan's summation algorithm to reduce error with floating point values
+  - `File.dirname` supports a new `level` argument
+- Vendor in `optparse` and `shellwords` ([#2326](https://github.com/opal/opal/pull/2326))
+- Preliminary support for compiling the whole `bin/opal` with Opal ([#2326](https://github.com/opal/opal/pull/2326))
+
+### Fixed
+
+- Fix coertion for `Array#drop` ([#2371](https://github.com/opal/opal/pull/2371))
+- Fix coertion for `File.absolute_path` ([#2372](https://github.com/opal/opal/pull/2372))
+- Fix some `IO#puts` edge cases (no args, empty array, nested array, …) ([#2372](https://github.com/opal/opal/pull/2372))
+- Preserve UNC path prefix on File.join ([#2366](https://github.com/opal/opal/pull/2366))
+- Methods on `Kernel`, `BasicObject`, `Boolean` will never return boxed values anymore ([#2293](https://github.com/opal/opal/pull/2293))
+  - `false.tap{}` will now correctly return a JS value of `false`, not `Object(false)`
+- opal-parser doesn't break on `<<~END` strings anymore ([#2364](https://github.com/opal/opal/pull/2364))
+- Fix error reporting at the early stage of loading ([#2326](https://github.com/opal/opal/pull/2326))
+
+### Changed
+
+- Various outputted code size optimizations - 19% improvement for minified unmangled AsciiDoctor bundle - see: https://opalrb.com/blog/2021/11/24/optimizing-opal-output-for-size/ ([#2356](https://github.com/opal/opal/pull/2356))
+- Second round of code size optimizations - 3% improvement for AsciiDoctor bundle on top of the first round - 23% total - see: https://github.com/opal/opal/pull/2365/commits ([#2365](https://github.com/opal/opal/pull/2365))
+  - The calls to `==`, `!=` and `===` changed their semantics slightly: it's impossible to monkey patch those calls for `String` and `Number`, but on other classes they can now return `nil` and it will be handled correctly
+  - The calls to `!` changed their semantics slightly: it's impossible to monkey patch this call for `Boolean` or `NilClass`.
+- Refactored the structure of the internal `stdlib/nodejs` folder ([#2374](https://github.com/opal/opal/pull/2374))
+  - Added `nodejs/base` with just I/O, exit, and ARGV management
+  - Moved `Process::Status` to corelib
+  - Fixed requires to be more robust
+
+### Removed
+
+- Removed `nodejs/irb` from stdlib as it's been broken for some time ([#2374](https://github.com/opal/opal/pull/2374))
+- Removed `Kernel#node_require` from `nodejs/kernel` as it's been deprecated for a long time ([#2374](https://github.com/opal/opal/pull/2374))
+
+<!--
+### Deprecated
+### Internal
+-->
+
+
+
+
+## [1.3.2](https://github.com/opal/opal/compare/v1.3.1...v1.3.2) - 2021-11-10
+
+
+### Fixed
+
+- Update documentation ([#2350](https://github.com/opal/opal/pull/2350))
+- Fix `IO#gets` getting an extra char under some circumstances ([#2349](https://github.com/opal/opal/pull/2349))
+- Raise a `TypeError` instead of `UndefinedMethod` if not a string is passed to `__send__` ([#2346](https://github.com/opal/opal/pull/2346))
+- Do not modify `$~` when calling `String#scan` from internal methods ([#2353](https://github.com/opal/opal/pull/2353))
+- Stop interpreting falsey values as a missing constant in `Module#const_get` ([#2354](https://github.com/opal/opal/pull/2354))
+
+
+
+
+## [1.3.1](https://github.com/opal/opal/compare/v1.3.0...v1.3.1) - 2021-11-03
+
+
+### Fixed
+
+- Fix REPL if bundler environment isn't set ([#2338](https://github.com/opal/opal/pull/2338))
+- Fix Chrome runner if bundler environment isn't set and make it work on other Unixes ([#2339](https://github.com/opal/opal/pull/2339))
+- `Proc#binding` to return a binding if `Binding` is defined (#2341, #2340)
+- `Array#zip` to correctly `yield` (#2342, #1611)
+- `String#scan` to correctly `yield` (#2342, #1660)
+
+
+
+
 ## [1.3.0](https://github.com/opal/opal/compare/v1.2.0...v1.3.0) - 2021-10-27
 
 
@@ -80,7 +185,7 @@ Changes are grouped as follows:
 ### Fixed
 
 - Fixed multiple line `Regexp` literal to not generate invalid syntax as JavaScript ([#1616](https://github.com/opal/opal/pull/1616))
-- Fix `Kernel#{try,catch}` along with `UncaughtThrowError` ([#2264](https://github.com/opal/opal/pull/2264))
+- Fix `Kernel#{throw,catch}` along with `UncaughtThrowError` ([#2264](https://github.com/opal/opal/pull/2264))
 - Update source-map-support to fix an off-by-one error ([#2264](https://github.com/opal/opal/pull/2264))
 - Source map: lines should start from 1, not 0 ([#2273](https://github.com/opal/opal/pull/2273))
 - Allow for multiple underscored args with the same name in strict mode ([#2292](https://github.com/opal/opal/pull/2292))
@@ -109,10 +214,6 @@ Changes are grouped as follows:
 - `Process` is now a Module, not a Class - just like in MRI ([#2332](https://github.com/opal/opal/pull/2332))
 - `s = StringIO.new("a"); s << "b"; s.string` now returns "b", like MRI, but Opal used to return "ab" ([#2309](https://github.com/opal/opal/pull/2309))
 
-### Deprecated
-
-### Removed
-
 ### Internal
 
 - Switch from jshint to ESLint ([#2289](https://github.com/opal/opal/pull/2289))

data/UNRELEASED.md

@@ -1,6 +1,8 @@
+<!--
 ### Added
 ### Fixed
 ### Changed
-### Deprecated
 ### Removed
+### Deprecated
 ### Internal
+-->

data/benchmark-ips/bm_truthy.rb

@@ -0,0 +1,30 @@
+Benchmark.ips do |x|
+  %x{
+    // Old version truthy logic
+    var old_version   = function(x) { return x !== nil && x != null && (!x.$$is_boolean || x == true); }
+
+    // New version truthy logic
+    var new_version_1 = function(val) { return undefined !== val && null !== val && false !== val && nil !== val && (!(val instanceof Boolean) || true === val.valueOf()); }
+
+    // Alternative new version truthy logic
+    var new_version_2 = function(val) { return undefined !== val && null !== val && false !== val && nil !== val && !(val instanceof Boolean && false === val.valueOf()); }
+
+    // Alternative new version, nil&false first
+    var new_version_3 = function(val) { return false !== val && nil !== val && undefined !== val && null !== val && !(val instanceof Boolean && false === val.valueOf()); }
+
+    // Alternative new version truthy logic that unsupports boxed booleans
+    var new_unboxed   = function(val) { return undefined !== val && null !== val && false !== val && nil !== val; }
+  }
+
+  values = [123,243,35,"sd",false,nil,123413234,120412,0,1234.1234,0.34,false,false,true,"sadfasf","","0",13,123,nil,Object.new,[]]
+
+  x.time = 32
+
+  x.report('old_version') { values.map(&`old_version`) }
+  x.report('new_version_1') { values.map(&`new_version_1`) }
+  x.report('new_version_2') { values.map(&`new_version_2`) }
+  x.report('new_version_3') { values.map(&`new_version_3`) }
+  x.report('new_unboxed') { values.map(&`new_unboxed`) }
+
+  x.compare!
+end

data/bin/opal-mspec

@@ -7,7 +7,5 @@ specs = ARGV.map do |s|
 end
 
 env = {}
-env['MSPEC_PATTERN'] = "{#{specs.join(',')}}" if specs.any?
+env['PATTERN'] = "{#{specs.join(',')}}" if specs.any?
 exec env, 'rake', 'mspec'
-
-# RUBYOPT="-rbundler/setup -rmspec/opal/special_calls" bundle exec mspec run -t opal -pspec/ruby/spec_helper spec/ruby/core/true/*

data/bin/opal-repl

@@ -1,4 +1,3 @@
 #!/usr/bin/env ruby
 
-require 'bundler/setup'
-load "#{__dir__}/../exe/opal-repl"
+exec "#{__dir__}/opal", '--repl', *ARGV

data/bin/remove-filters

@@ -15,10 +15,7 @@
 #  5) "Set#filter! returns nil when self was not modified"
 
 filters = $stdin.read.split("\n").map do |i|
-  # This special example should be rather moved to unsupported for now...
-  next if i =~ /formats the local time following the pattern/
-
-  i.scan(/\d+\) (".*")/).first.first
+  i.scan(/(?:\d+\)|fails) (".*")/).first.first
 end.compact
 filters = Regexp.union(*filters)
 

data/docs/compiled_ruby.md

@@ -30,8 +30,8 @@ to convert values to opal specific values.
 
 NOTE: Because `true` and `false` compile to their native
 javascript equivalents, they must share the same class: `Boolean`.
-For this reason, they do not belong to their respective `TrueClass`
-and `FalseClass` classes from ruby.
+Thru some level of hackery, we make them pseudo-members of the appropriate
+`TrueClass` and `FalseClass`.
 
 #### Strings & Symbols
 
@@ -55,11 +55,11 @@ class. Symbols and Strings can therefore be used interchangeably.
 
 #### Numbers
 
-In Opal there is a single class for numbers; `Numeric`. To keep Opal
+In Opal there is a single class for numbers; `Number`. To keep Opal
 as performant as possible, Ruby numbers are mapped to native numbers.
 This has the side effect that all numbers must be of the same class.
-Most relevant methods from `Integer`, `Float` and `Numeric` are
-implemented on this class.
+Most relevant methods from `Integer` and `Float` are implemented on
+this class.
 
 ```ruby
 42        # => 42
@@ -104,7 +104,7 @@ else is a truthy value including `""`, `0` and `[]`. This differs from
 JavaScript as these values are also treated as false.
 
 For this reason, most truthy tests must check if values are `false` or
-`nil`.
+`nil` (we also check for `null` and `undefined`).
 
 Taking the following test:
 
@@ -178,15 +178,19 @@ puts "foo"
 This would compile directly into:
 
 ```javascript
-(function(Opal) {
-  var self = Opal.top, $nesting = [], nil = Opal.nil, $breaker = Opal.breaker, $slice = Opal.slice;
+Opal.queue(function(Opal) {
+  var self = Opal.top, nil = Opal.nil;
 
-  Opal.add_stubs(['$puts']);
+  Opal.add_stubs('puts');
   return self.$puts("foo")
-})(Opal);
+});
 ```
 
-**TIP:** you can see the compiled code with this command: `opal --compile --no-exit --no-opal --eval 'puts "foo"'`
+**TIP:**
+
+you can see the compiled code with this command: `opal --compile --no-exit --no-opal --eval 'puts "foo"'`
+or, more briefly: `opal -cEO -e 'puts "foo"'`
+
 
 ### Using compiled sources
 
@@ -204,16 +208,16 @@ obvious what went wrong.
 
 As Opal just generates JavaScript, it is useful to use a native
 debugger to work through JavaScript code. To use a debugger, simply
-add an x-string similar to the following at the place you wish to
-debug:
+add a `debugger` statement:
 
 ```ruby
 # .. code
-`debugger`
+debugger
 # .. more code
 ```
-The x-strings just pass the debugger statement straight through to the
-JavaScript output.
+
+The `debugger` statement is compiled to become a JavaScript `debugger`
+statement. This statement breaks the code if you have your Inspector open.
 
 NOTE: All local variables and method/block arguments also keep their Ruby
 names except in the rare cases when the name is reserved in JavaScript.
@@ -246,7 +250,7 @@ in the browser.
 }
 
 # => opal version is:
-# => 0.6.0
+# => 1.3.1
 ```
 
 Even interpolations are supported, as seen here.
@@ -280,6 +284,9 @@ require 'native'
 win = Native(`window`) # equivalent to Native::Object.new(`window`)
 ```
 
+To access a Native-wrapped global JavaScript object, we can also use `$$`, after
+we have the `native` module required.
+
 Now what if we want to access one of its properties?
 
 ```ruby
@@ -514,10 +521,10 @@ Opal.BAZ;          // => 789
 To reach nested constants the safest way is to call `#const_get` on `Object`:
 
 ```javascript
-Opal.Object.$$const_get('Bar::BAR'); // => 123
-Opal.Object.$$const_get('Foo::BAR'); // => 123
-Opal.Object.$$const_get('Foo::FOO'); // => 456
-Opal.Object.$$const_get('BAZ');      // => 789
+Opal.Object.$const_get('Bar::BAR'); // => 123
+Opal.Object.$const_get('Foo::BAR'); // => 123
+Opal.Object.$const_get('Foo::FOO'); // => 456
+Opal.Object.$const_get('BAZ');      // => 789
 ```
 
 Constants can also be navigated using the `$$` property, although this is limited to constants defined directly under the current object:
@@ -528,6 +535,14 @@ Opal.Foo.$$.FOO // => 456
 Opal.Foo.$$.BAR // => undefined
 ```
 
+A later feature also allows you to skip the `$$` property:
+
+```javascript
+Opal.Bar.BAR // => 123
+Opal.Foo.FOO // => 456
+Opal.Foo.BAR // => undefined
+```
+
 
 ### Calling methods
 
@@ -656,7 +671,7 @@ It is obvious from here, that unless an object defines any given method, it will
 To optimise the generated code slightly, we reduce the code output from the compiler into the following JavaScript:
 
 ```javascript
-Opal.add_stubs(["first", "second", "to_sym"]);
+Opal.add_stubs("first,second,to_sym"]);
 ```
 
 You will see this at the top of all your generated JavaScript files. This will add a stub method for all methods used in your file.

data/docs/faq.md

@@ -10,7 +10,7 @@ We run opal against the [ruby spec](https://github.com/ruby/spec) as our primary
 
 ### What version of ruby does Opal target?
 
-We are running tests under ruby 2.0.0 conditions, but are mostly compatible with 1.9 level features.
+We are running tests under ruby 3.0.0 conditions, but are mostly compatible with 2.6 level features.
 
 ### Why doesn't Opal support mutable strings?
 

data/docs/headless_chrome.md

@@ -3,7 +3,6 @@
 ## Requirements
 
 First of all, make sure that you have Chrome at least 59.0 installed.
-Also for now it's supported only on Mac and Linux. (version 60 may get support on Windows)
 
 ## Using the runner
 
@@ -22,11 +21,9 @@ The runner also listens for any exceptions and prints formatted stracktraces bac
     raising_method
     "
 
-    RuntimeError : test error
-        at $$raise (file:///tmp/chrome-opal.js:4996:6)
-        at $$raising_method (file:///tmp/chrome-opal.js:21144:16)
-        at  (file:///tmp/chrome-opal.js:21146:14)
-        at  (file:///tmp/chrome-opal.js:21147:2)
+    RuntimeError: test error
+      from <internal:corelib/…>:2693:7:in `<main>'
+      from -e:1:1:in `undefined'
 
 ## Using exit codes
 
@@ -36,10 +33,9 @@ By default headless chrome runner explicitly sets exit code to 1 when there was
     0
 
     $ opal -Rchrome -e "raise 'error'"; echo $?
-    RuntimeError : error
-        at $$raise (file:///tmp/chrome-opal.js:4996:6)
-        at  (file:///tmp/chrome-opal.js:21139:14)
-        at  (file:///tmp/chrome-opal.js:21140:2)
+    RuntimeError: error
+      from <internal:corelib/kerne…>:2693:7:in `<main>'
+      from -e:1:1:in `undefined'
     1
 
 You can change final exit code by using `Kernel#exit`, but make sure to require `opal/platform` in your code.
@@ -69,20 +65,12 @@ or runs the server on its own. It detects your platform and uses a default path
 (`Opal::CliRunners::Chrome#chrome_executable`) but you can override it by specifying `GOOGLE_CHROME_BINARY` environment
 variable.
 
-When the server is up and running it passes compiled js code to `node lib/opal/cli_runners/chrome.js`
+When the server is up and running it passes compiled js code to `lib/opal/cli_runners/chrome_cdp_interface.rb`
 as a plain input using stdin (basically, it's a second part of the runner).
-`chrome.js` is a node js script that does the main job. It runs any provided code on the running chrome server,
+`chrome_cdp_interface.rb` is a node js + Opal script that does the main job. It runs any provided code on the running chrome server,
 catches errors and forwards console messages.
 
 
-Moreover, you can actually call any js using headless chrome by running
-
-      $ echo "console.log('Hello, Opal')" | node lib/opal/cli_runners/chrome.js
-
-NOTE: to run it you need to have a chrome server running on `localhost:9222` (usually `chrome.rb` does it for you)
-
-      $ chrome --disable-gpu --headless --remote-debugging-port=9222
-
 ## Using a remote chrome server
 
 If you want to change a default chrome port or your chrome server is running on a different host:port
@@ -99,7 +87,9 @@ NOTE: `CHROME_HOST` requires a chrome server to be started. You can't start remo
 
 If you need to pass additional CLI options to the Chrome executable you can do so by setting the `CHROME_OPTS` environment variable:
 
-      $ CHROME_OPS="--window-size=412,732" opal -Rchrome -e "puts 42"
+      $ CHROME_OPTS="--window-size=412,732" opal -Rchrome -e "puts 42"
       42
 
+Docker users may need `CHROME_OPTS="--no-sandbox"` due to the user namespaces limitations.
+
 _For a list of additional options see https://developers.google.com/web/updates/2017/04/headless-chrome_

data/docs/jquery.md

@@ -1,8 +1,6 @@
 # JQuery
 
-`opal-jquery` offers a nicer ruby-like syntax for JQuery (and Zepto). It is
-useful for projects which cannot use `opal-browser` due to a reliance on jquery
-for plugins or other libraries.
+`opal-jquery` offers a nicer ruby-like syntax for JQuery. It is useful for projects which cannot use `opal-browser` due to a reliance on jquery for plugins or other libraries.
 
 ```ruby
 foos = Element.find('.foo')
@@ -91,9 +89,6 @@ bridged instances of jquery objects. Just like ruby arrays are just javascript
 arrays, `Element` instances are just jquery objects. This makes interaction
 with jquery plugins much easier.
 
-Also, `Element` will try to bridge with Zepto if it cannot find jQuery loaded,
-making it ideal for mobile applications as well.
-
 ### Interacting with the DOM
 
 #### Finding Elements

data/docs/opal_parser.md

@@ -8,12 +8,14 @@ Opal is able to compile its – pure Ruby – compiler to JavaScript (how cool i
 require 'opal-parser'
 ```
 
+_Note: For the best performance and application load times, it is strongly recommended to design your application so that it won't need the parser. A lot of methods described in this document are more fun hacks than robust solutions. But if you really want or need to use them, for example so that you can implement a Ruby REPL or an interactive Ruby playground - we have you covered, but for all other cases, we strongly discourage you to take an advice from this guide._
+
 
 ## Features
 
 ### `Kernel#eval`
 
-`opal-parser` provides a partial implementation of `Kernel#eval` that only support the first parameter (String) and refuse any passed `binding`, `lineno` or `filename`.
+`opal-parser` provides a partial implementation of `Kernel#eval`.
 
 Example:
 

data/docs/promises.md

@@ -8,6 +8,8 @@ It can be required inside any Opal applicaton:
 require 'promise'
 ```
 
+_Please also take a look at the Asynchronous code guide - we are in the process of modernizing the Promises, along with supporting async/await_
+
 ## Usage
 
 This example shows how to use a `HTTP` request from `opal-jquery` from a callback style, into a promise style handler.

data/docs/releasing.md

@@ -11,8 +11,26 @@ _This guide is a work-in-progress._
 
 - Ensure all the unreleased changes are documented in UNRELEASED.md
 - Run `bin/rake changelog VERSION=v1.2.3` specifying the version number you're about to release
+- Empty UNRELEASED.md
 
 ## The commit
 
-- Commit the updated changelog along with the version bump using this commmit message:
+- Commit the updated changelog along with the version bump using this commit message:
   "Release v1.2.3"
+- Push the commit and run `bin/rake release` to release the new version to Rubygems
+- Go to GitHub releases and create a new release from the latest tag pasting the contents from CHANGELOG.md
+
+## Opal docs
+
+- Open `opal-docs` and run `bin/build v1.2.3`
+- Then run `bin/deploy`
+
+## Opal site
+
+- Open `opal.github.io` and update the opal version in the `Gemfile`
+- run `bin/build`
+- `git push` the latest changes
+
+## Opal CDN
+
+- Run `bin/release v1.2.3`

data/docs/roda-sprockets.md

@@ -23,7 +23,6 @@ class App < Roda
    plugin :sprockets, precompile: %w(application.js),
                       prefix: %w(app/),
                       opal: true,
-                      debug: ENV['RACK_ENV'] != 'production'
    plugin :public
 
    route do |r|

data/docs/source_maps.md

@@ -1,10 +1,6 @@
 # Source maps
 
-Source maps are available (on current stable release, v0.6.x) even without explicit support from Sprockets in a sort of hackish way.
-
-_As such even if they generally work fine there are some limitations and edge case issues._
-
-NOTE: Currently on `master` branch sourcemaps are work-in-progress and probably will integrate with the upcoming Sprockets 4 that has integrated support for them.
+Source maps are available on most environments we support.
 
 #### Processor `source_map_enabled` flag
 To enable sourcemaps in the Sprockets processor you need to turn on the relative flag:
@@ -16,8 +12,7 @@ Opal::Config.source_map_enabled = true # default
 
 #### Sprockets debug mode
 
-The  sourcemaps only work with Sprockets in debug mode because they are generated just for single files.
-
+The source maps only work with Sprockets in debug mode - this is a limitation of Sprockets.
 
 ## Enable source maps
 
@@ -37,13 +32,17 @@ config.assets.debug = true
 
 ### Sinatra
 
-You can add `Opal::Server` as in the official example: [sinatra/config.ru](https://github.com/opal/opal/blob/0-6-stable/examples/sinatra/config.ru).
+You can add `Opal::Server` as in the official example: [sinatra/config.ru](https://github.com/opal/opal/blob/master/examples/sinatra/config.ru).
 
 ### Opal::Server
 
-`Opal::Server` implements sourcemaps and can be used alone or with `Rack::Cascade` in conjunction with other apps.
+`Opal::Server` (which is based on Sprockets) implements sourcemaps and can be used alone or with `Rack::Cascade` in conjunction with other apps.
+
+### Opal::SimpleServer
+
+Like `Opal::Server`, `Opal::SimpleServer` (which isn't based on Sprockets) implements sourcemaps properly.
 
-### Opal::Environment
+### Opal::Builder
 
-`Opal::Environment` is a bit lower level and doesn't support source maps by itself.
+`Opal::Builder` is a bit lower level and doesn't support source maps by itself. It requires you to call in a specific method to generate them yourself.
 

data/docs/static_applications.md

@@ -2,7 +2,7 @@
 
 `opal` makes it easy to build static opal applications. Opal uses internal load
 paths to make it easy to handle resolving requirements during building. `opal`
-forms the basis of rails support, so anything you can do there, you can do
+forms the basis of Rails support, so anything you can do there, you can do
 standalone as well.
 
 ## Overview
@@ -11,7 +11,7 @@ First, install `opal` adding them to a `Gemfile`:
 
 ```ruby
 # Gemfile
-gem "opal", "~> 0.7.0"
+gem "opal"
 ```
 
 Next, we want to add our main app code. Keep all opal code inside `app/`

data/docs/unsupported_features.md

@@ -6,6 +6,10 @@ Opal does not support some language/runtime features of ruby. These are document
 
 For performance and ease of runtime features, all strings in Opal are immutable, i.e. `#<<`, `#gsub!`, etc. do not exist. Also, symbols are just strings. There is no class, runtime or feature difference between Symbols and Strings. Their syntaxes can be used interchangeably.
 
+#### Regexp differences ####
+
+We are using JavaScript regular expressions. While we do translate a few of Ruby specific instructions like `\A` or `\z`, there are a lot of incompatibilities that you should be aware of - for example `$` and `^` don't match newlines like they do in Ruby. Support for features like named matches or lookahead/lookbehind is dependent on the JavaScript environment support for those. To support everything, we would need to [compile in the entire Ruby's regular expression engine](https://opalrb.com/blog/2021/06/26/webassembly-and-advanced-regexp-with-opal/) which is unfeasible at the current time.
+
 #### Integer / Float difference ####
 
 In Opal, both integers and floats belong to same class `Number` (using JavaScript native numbers). So `1 / 4` is `0.25` (not `0`) and `4.0 / 2` is `2` (not `2.0`).

data/exe/opal-repl

@@ -1,5 +1,3 @@
 #!/usr/bin/env ruby
 
-ARGV << "--repl"
-
-load __dir__+"/opal"
+exec "#{__dir__}/opal", '--repl', *ARGV

data/lib/opal/ast/builder.rb

@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 require 'opal/ast/node'
-require 'parser/ruby30'
+require 'parser/ruby31'
 
 module Opal
   module AST