[node/module] (nodejs v12 and v13) Add missing types for custom require and require.cache

[GeorgeTaveras1231]

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change. (Run with npm test.)
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm run lint package-name (or tsc if no tslint.json is present).

Select one of these and delete the others:

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes:

  https://nodejs.org/api/modules.html#modules_module_createrequire_filename
  follow the link to the return value, see that it has the same API as the global require

• If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the header.
• If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }. If for reason the any rule need to be disabled, disable it for that line using // tslint:disable-next-line [ruleName] and not for whole package so that the need for disabling can be reviewed.

[typescript-bot]

@GeorgeTaveras1231 Thank you for submitting this PR!

🔔 @microsoft @DefinitelyTyped @jkomyno @a-tarasyuk @alvis @r3nya @btoueg @BrunoScheufler @smac89 @tellnes @Touffy @DeividasBakanas @eyqs @Flarna @Hannes-Magnusson-CK @KSXGitHub @hoo29 @kjin @ajafff @islishude @mwiktorczyk @mohsen1 @n-e @octo-sniffle @galkin @parambirs @eps1lon @SimonSchick @ThomasdenH @WilcoBakker @wwwy3y3 @ZaneHannanAU @samuela @kuehlein @j-oliveras @bhongy @chyzwar @trivikr @nguymin4 - please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

If no reviewer appears after a week, a DefinitelyTyped maintainer will review the PR instead.

[typescript-bot]

@GeorgeTaveras1231 The Travis CI build failed! Please review the logs for more information.

Once you've pushed the fixes, the build will automatically re-run. Thanks!

[galkin]

Looks good for me.

[GeorgeTaveras1231]

@DefinitelyTyped I'm having a hard time seeing the connection between my changes and the failing benchmark CI check. I'm happy to make the necessary changes, but my first reaction is to assume there is a larger problem with the CI check, that's out of scope from this PR. Is that assumption correct? If not, I can spend a little longer looking into the error.

[Flarna]

@GeorgeTaveras1231 The fail looks unrelated, unforuntatelly CI is flaky here.
Best is to retrigger CI by closing and reopening the PR or pushing a commit and hope that it

[typescript-bot]

A definition owner has approved this PR ⭐️. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait. Thank you for your contribution to DefinitelyTyped!

[Flarna]

@sheetalkamat @sandersn Could you please take a look into the failing BenchmarkPR runs?

Doesn't look related to the change done in this PR but failing CI builds (even Benchmarks) block merge (see #40263)

Error: Error: Command failed: npm install --ignore-scripts --no-shrinkwrap --no-package-lock --no-bin-links
npm ERR! code ENOENT
npm ERR! syscall lchown
npm ERR! path /home/vsts/.npm/_locks/staging-b3823d1922361c5d.lock
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, lchown '/home/vsts/.npm/_locks/staging-b3823d1922361c5d.lock'

[SimonSchick]

@Flarna rel https://github.com/microsoft/types-publisher/issues/707

[typescript-bot]

👋 Hi there! I’ve run some quick measurements against master and your PR. These metrics should help the humans reviewing this PR gauge whether it might negatively affect compile times or editor responsiveness for users who install these typings.

Let’s review the numbers, shall we?

Comparison details 📊

	master	#40456	diff
Batch compilation
Memory usage (MiB)	123.1	122.0	-0.9%
Type count	21636	21642	0%
Assignability cache size	39461	39463	0%
Language service
Samples taken	1653	1689	+2%
Identifiers in tests	11517	11553	0%
getCompletionsAtPosition
Mean duration (ms)	686.1	679.6	-1.0%
Mean CV	6.9%	6.8%
Worst duration (ms)	889.1	844.6	-5.0%
Worst identifier	SSL_OP_MICROSOFT_BIG_SSLV3_BUFFER	S_IFSOCK
getQuickInfoAtPosition
Mean duration (ms)	679.9	674.3	-0.8%
Mean CV	6.9%	6.9%	+0.8%
Worst duration (ms)	848.3	850.4	+0.2%
Worst identifier	debug	URLSearchParams

It looks like nothing changed too much. I won’t post performance data again unless it gets worse.

[typescript-bot]

I just published @types/[email protected] to npm.