window object definition about devtool HOT 7 CLOSED

Yeah, it's a bit tricky. That sort of existence check is very fragile, as there are lots of solutions nowadays that blend browser/Node features like process and require.

Do you have any modules in particular that are breaking or acting strangely? It would be good to test against real-world use cases rather than hypotheticals.

from devtool.

The module that borked things up for me was https://github.com/mio/mio.

Perhaps https://github.com/facebook/react might be useful to check out?

from devtool.

Here's a bit of a wacky idea... could you wrap all of the app's code in an IIFE to override the window variable like so?

(function (window) {
  // app code goes here...
  console.log(window) // undefined!
})()

from devtool.

Yes I was thinking the same. We are already wrapping the code in closures anyways for Node requires. It will break the odd app that does something like this, but it's fairly non standard:

// module A
global.window = 'foo';

// module B
console.log(window);

It would probably come in through a flag like --no-browser-globals (or maybe something more concise than that!) which also removes document and other things.

from devtool.

Also it will mean window.close() is not possible.

from devtool.

Pushed no-browser-globals branch.

You can try it like so:

npm i Jam3/devtool#no-browser-globals -g
devtool my-file.js --no-bg

This doesn't work in the REPL/Console, though. Going to sit on it for a while and think if there is any other way to fix this.

from devtool.

Pushed to 1.6.0

from devtool.