vhad/DefinitelyTyped
1
0
Fork 0
mirror of https://github.com/gosticks/DefinitelyTyped.git synced 2025-10-16 12:05:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix node and webpack-env compatibility (#41313)

Browse Source 
* Fix node and webpack-env compatibility

* Fix missing update
This commit is contained in:
Andrew Branch 2020-01-03 17:28:52 -06:00 committed by Nathan Shively-Sanders
parent 57248c2857
commit ec7421505e
2 changed files with 16 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
types/node/globals.d.ts vendored
View File

@ -164,8 +164,8 @@ declare function clearImmediate(immediateId: NodeJS.Immediate): void;
declare function queueMicrotask(callback: () => void): void;
declare var require: NodeJS.Require;
declare var module: NodeJS.Module;
declare var require: NodeRequire;
declare var module: NodeModule;
// Same as module.exports
declare var exports: any;

24
types/webpack-env/index.d.ts vendored
View File

@ -1,4 +1,4 @@
// Type definitions for webpack (module API) 1.14
// Type definitions for webpack (module API) 1.15
// Project: https://github.com/webpack/webpack
// Definitions by: use-strict <https://github.com/use-strict>
// rhonsby <https://github.com/rhonsby>
@ -10,6 +10,10 @@
*/
declare namespace __WebpackModuleApi {
interface RequireResolve {
(id: string): string | number;
}
interface RequireContext {
keys(): string[];
(id: string): any;
@ -42,7 +46,7 @@ declare namespace __WebpackModuleApi {
*
* The module id is a number in webpack (in contrast to node.js where it is a string, the filename).
*/
resolve(path: string): number | string;
resolve: NodeJS.RequireResolve;
/**
* Like require.resolve, but doesn’t include the module into the bundle. It’s a weak dependency.
*/
@ -55,19 +59,17 @@ declare namespace __WebpackModuleApi {
* Multiple requires to the same module result in only one module execution and only one export. Therefore a cache in the runtime exists. Removing values from this cache cause new module execution and a new export. This is only needed in rare cases (for compatibility!).
*/
cache: {
[id: string]: any;
[id: string]: NodeModule;
}
}
interface Module {
exports: any;
require(id: string): any;
require<T>(id: string): T;
id: string;
filename: string;
loaded: boolean;
parent: any;
children: any[];
parent: NodeModule | null;
children: NodeModule[];
hot?: Hot;
}
type ModuleId = string|number;
@ -276,8 +278,7 @@ declare namespace __WebpackModuleApi {
type RequireLambda = __Require1 & __Require2;
}
interface NodeRequire extends __WebpackModuleApi.RequireFunction {
}
interface NodeRequire extends NodeJS.Require {}
declare var require: NodeRequire;
@ -328,7 +329,7 @@ declare var __non_webpack_require__: any;
*/
declare var DEBUG: boolean;
interface NodeModule extends __WebpackModuleApi.Module {}
interface NodeModule extends NodeJS.Module {}
declare var module: NodeModule;
@ -337,5 +338,8 @@ declare var module: NodeModule;
*/
declare namespace NodeJS {
interface Process extends __WebpackModuleApi.NodeProcess {}
interface RequireResolve extends __WebpackModuleApi.RequireResolve {}
interface Module extends __WebpackModuleApi.Module {}
interface Require extends __WebpackModuleApi.RequireFunction {}
}
declare var process: NodeJS.Process;