Tim Caswell comments

Results 341 comments of


                                            Tim Caswell

require fallback doesn't seem to work

Agreed, maybe we should consider luvit 3.0 at some point. Maybe next time I'm working on a project that uses luvit I can spend more time on it.

require fallback doesn't seem to work

But if someone else wants to drive it, I can give advice/opinion.

attempt to index global 'process' (a nil value)

The stream module probably shouldn't depend on `_G.process` from luvit core. But I'm curious, how are you bootstrapping your luvi app? The luvit main function is supposed to setup the...

attempt to index global 'process' (a nil value)

Running luvit from unzipped tree should be the same as from zip directly. I'm not sure what exactly you're doing.

attempt to index global 'process' (a nil value)

Also what's probably missing from that example, is luvi used to auto-detect and bootstrap `deps/require.lua` if it existed. I'm not sure this is the case anymore. Look at luvit's main...

attempt to index global 'process' (a nil value)

Also, thanks @squeek502 for helping! My whole family has the flu and I'm a bit under the weather. Also expecting our 5th child any day now.

process:on(...) - attempt to call method 'on' (a nil value)

Strange Indeed.

process:on(...) - attempt to call method 'on' (a nil value)

I remember now! (almost two weeks of vacation take a bit to come back from) The global `process` is the return value of `require('process').globalProcess()`. If you replace it with the...

process:on(...) - attempt to call method 'on' (a nil value)

Regarding the auto-require behavior of the repl, this might be a problem since the default `process` in the repl is not the same as in a luvit script.

process:on(...) - attempt to call method 'on' (a nil value)

@kaustavha that's one idea. Another is to change the process module to export the global process directly. I'm not sure why it's designed this way.