These are chat archives for opal/opal

13th
Jan 2018
G. Gibson
@mistergibson
Jan 13 2018 00:11
I'm not sure if it is a) pilot error (most likely), b) opal-browser bug, or c) opal bug.
G. Gibson
@mistergibson
Jan 13 2018 05:53
OK - figured it out. Pilot error as usual. Odd thing though - even though I required 'browser/socket' in the bootstrap file compiled to .js - I had to do a Opal.eval("require 'browser/socket'); to make the constant get defined in the Browser console.
is this a lazy-loading feature?
Elia Schito
@elia
Jan 13 2018 21:37
That’s strange, can you share the whole code and compiling process?
G. Gibson
@mistergibson
Jan 13 2018 21:56
Sure, I'll whip up a gist on it all
G. Gibson
@mistergibson
Jan 13 2018 22:03
Here you go - this is what I did and what I got: https://gist.github.com/mistergibson/37f7a3f0afbd19b1d138d1544ca5ac5a
G. Gibson
@mistergibson
Jan 13 2018 22:12
Also note: when I just did a compile with '--gem opal-browser' instead of including the two dirs, I'd get 'add_method' undefined for Opal in the Browser.