Fix: Use global instead of window

Question

I am trying a component inside runkit.com. As it is visible from the image, the platform tells me ...

Fix: Use global instead of window. RunKit is a node environment, so window and other browser features won’t exist. If you’re just trying to access the global object, you can simply use global instead.

This is the code pasted:

var window = {};
const QueryQl = require("queryfilters/queryql")
var q = new QueryQl();
q.json({
    'ciao': 'mondo'
});
q.getQueryString();

How can I fix this?

@JonasW. As the error is a ReferenceError defining window may be the solution, Without needing for editing the module. — , Jan 06 '18 at 11:01

score 1 · Answer 1 · answered Jan 06 '18 at 10:52

1

The fix is simple. Just replace this

window.module = window.module || {};

with this:

global.module = global.module || {};

in the module.

answered Jan 06 '18 at 10:52

sensorario

20,262
30
97
159

With every update to the module you will have to replace it again! – Jan 06 '18 at 11:32

score 0 · Answer 2 · answered Jan 06 '18 at 10:56

0

Try to define window to the global, Before calling the module:

global.window = {}

answered Jan 06 '18 at 10:56

Fix: Use global instead of window

2 Answers2