Recommended approach for globally setting undefined

[jackjocross]

First off, thank you for this helpful package!

Using Babel, undefined is scoped to the module that I import it in, but I want undefined to be a function for my entire site. My current approach is:

import { undefined as undef } from 'undefined-is-a-function';

undefined = undef;

If this is a common use case would you consider adding a utility method?

[donavon]

Hmmm... Seems like a lot of manual work. What if it were abstracted away using a helper function? Something like this (just spitballing here):

import { undefined, setGlobal } from 'undefined-is-a-function';
setGlobal('undefined', undefined);

PRs welcome. 😉

[maniator]

@crosscompile you would have to do :

global.undefined = undef;

// or:
window.undefined = undef;

[aarongodin]

Following the single-responsibility principle, we should probably create a new package on npm called undefined-is-always-a-function. This package already has enough code in it. We wouldn't want our complexity to go up too much.

[jackjocross]

After further investigation, I think we might have a slight issue. According to MDN, modern browsers implement undefined as a non-configurable, non-writable property.

Not sure if this is intended to be a helpful "feature", but we might need to explore other methods to globally set undefined.

[maniator]

😞

[maniator]

Although, this does work:

So you would have to do it in a module pattern. or like define it using webpack defines or something?

[jackjocross]

@maniator I was thinking the same, maybe a webpack plugin or babel transform that defines undefined as a function in each module.

[jackjocross]

I present, in all it's glory, babel-plugin-undefined-is-always-a-function.