Getting an Namespace 'NodeJS' has no exported member 'Global' error

[robgeurden]

🐛 Bug Report

When trying to build our solution we get the following error:
Namespace 'NodeJS' has no exported member 'Global' on line node_modules/@jest/types/build/Global.d.ts:85:62

Seems to be coming from https://github.com/facebook/jest/blob/master/packages/jest-types/src/Global.ts line 137

To Reproduce

Version of node 14.16.1 & Jest 27.0.6

Expected behavior

Not to get this error when building

Link to repl or repo (highly encouraged)

https://github.com/robgeurden/easy-test

[sachinahya]

We just came across this too when our CI builds started failing. Looks like NodeJS.Global namespace was removed in @types/node 16.0.0 and @jest/types is broken because it specifies any version in its package.json.

Managed to work around it by adding "@types/node": "^15.14.1" to our package.json dependencies.

[SimonSchick]

NodeJS.Global should probably be replaced w/ typeof globalThis

[splincode]

hello, I have a problem with it

[mrcnski]

Can a maintainer please provide an update on this? This is causing ecosystem-wide disruption. I've documented only a few instances here. Someone has graciously provided a fix here yet official maintainers have been silent.

Also, what is being done to ensure that this does not occur again in the future?

[nyan-left]

Also experiencing this issue.

[SimonSchick]

If this issue isn't addressed by tomorrow I will work on adding a a small compatibility layer to v16, the preferred approach however is for people to to stick to v15 for now.

[aterreno]

Just hit this as well after upgrading to jest 27 from jest 26

[fouchekeagan]

I worked around this by adding "@types/node@15.12.2" as a dependency.
Command: npm i @types/node@15.12.2 --save-dev

Using Jest 27:

I hope this helps someone until the issue is resolved. :)

[aterreno]

@fouchekeagan yep that's exactly how we fixed it, if you are on node types @16 it won't work thanks for sharing

[sandersn]

NodeJS.Global is exported in five places:

jest-fake-timers: legacyFakeTimers.ts
jest-fake-timers: modernFakeTimers.ts
jest-types/src/Config.ts
jest-types/src/Global.ts
jest-mock/src/index.ts

But there are quite a few more in the tests.

globalThis was introduced in Typescript 3.4, March 2019. TS 3.3 is outside the 2-year support window for Definitely Typed (which is why I ran into it -- everything on DT needs to support @types/node@16), although I'm not sure what versions jest tries to support.

Edit: I tried upgrading jest to node 16 types but got stuck (1) because of other node 16 changes (2) the difference between places that accept either globals or Window, or require both globals and Window.

[ghost]

NodeJS.Global should probably be replaced w/ typeof globalThis

interface CustomNodeJsGlobal extends NodeJS.Global {
  foo: {
    bar: string | null
  }
}

@SimonSchick How'd you do it?

[SimonSchick]

global { // declarations }, pls see the typescript manual.

[signal-intrusion]

@SimonSchick I may have misunderstood. The fix has been shipped?

I was only able to make this work by installing @types/node@15.x. I've read the relevant typescript docs many times and tried many, many permutations (https://www.typescriptlang.org/docs/handbook/declaration-files/templates/global-d-ts.html).

I want to type this:

// file.ts
global.thing = {
        logging: new Logger(),
        version: version
}

This is the original global.d.ts, which works in @types/node@15:

// global.d.ts
declare global {
    module NodeJS {
        interface Global {
            thing: {
                logging: Logger,
                version: string
            }
        }
    }
}

With @types/node@16 I get the following error: Element implicitly has an 'any' type because type 'typeof globalThis' has no index signature.

Things I've tried:

declare global {
    interface globalThis {
        thing: {
            logging: Logger,
            version: string
        }
    }
}

declare global {
    interface thing {
        logging: Logger,
        version: string
    }
}

declare global {
    interface Global {
        thing: {
            logging: Logger,
            version: string
        }
    }
}

interface thing: {
    logging: Logger,
    version: string
}

// etc.

(global as Global).thing = {
        logging: new Logger(),
        version: version
}

(global as globalThis).thing = {
        logging: new Logger(),
        version: version
}

(global as Window).thing = {
        logging: new Logger(),
        version: version
}

I've been at this for a few hours now and I just can't figure it out.

I mean @types/node@15 works and so does: (global as unknown as Window).thing = {} 🤷

[SimonSchick]

All global MUST be declared w/ var eg.

declare global {
  var myGlobal: number;
}

Please read the documentation

[G-Rath]

I feel like we might have gotten a bit sidetracked, so looping back around to the original error:

@SimonSchick you said previously:

If this issue isn't addressed by tomorrow I will work on adding a a small compatibility layer to v16

Did you end up doing this? I can't see any strong evidence that you did, and for me type checking is still broken using the latest v16 types, but wanted to double check in case I'd missed something.

I've been able to resolve the problem locally with the following:

declare global {
  namespace NodeJS {
    interface Global {}
  }
}

Which should suffice as a temporary workaround to allow compiling & typechecking in downstream projects.

[waynevanson]

I've been able to resolve the problem locally with the following:

declare global {
  namespace NodeJS {
    interface Global {}
  }
}

Which should suffice as a temporary workaround to allow compiling & typechecking in downstream projects.

I had to do the following to get mine to work, as I'm building a custom reporter and preset.

// https://github.com/facebook/jest/issues/11640#issuecomment-893867514
declare global {
  namespace NodeJS {
    interface Global {}
    interface InspectOptions {}

    interface ConsoleConstructor
      extends console.ConsoleConstructor {}
  }
}

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.