typescript-typings

问题 I'm writing a React app using TypeScript. I use material-ui for my components. I'm writing a custom wrapper for material-ui's Button component. It looks like this: import MUIButton, { ButtonProps } from "@material-ui/core/Button"; import withStyles, { WithStyles } from "@material-ui/core/styles/withStyles"; import classNames from "classnames"; import React, { PureComponent } from "react"; import styles from "./styles"; export interface OwnProps { color: "primary" | "danger" | "warning" |

问题 I'm working on a JavaScript transpiler that apart from other things will also replace certain functions and variables upon build. For example the following file ( ./src/my-module.js ): defineModule("MyModule", function(exports) { return exports; }); Will be copied and converted to ( ./build/my-module.js ): (function(global, factory) { "use strict"; if (typeof exports !== "undefined" && typeof module !== "undefined") module.exports.MyModule = factory(exports.MyModule || {}); else factory

问题 I'm working on a JavaScript transpiler that apart from other things will also replace certain functions and variables upon build. For example the following file ( ./src/my-module.js ): defineModule("MyModule", function(exports) { return exports; }); Will be copied and converted to ( ./build/my-module.js ): (function(global, factory) { "use strict"; if (typeof exports !== "undefined" && typeof module !== "undefined") module.exports.MyModule = factory(exports.MyModule || {}); else factory

问题 Consider a tuple like this: type MyTuple = [A, B]; where A and B both have an attribute named key . For instance, interface A = { key: 'sandwiches' } interface B = { key: 'pasta' } I desire the following interface: interface Result { sandwiches: A; pasta: B; } Is there a way to do this dynamically? I'm thinking that, if this is achievable, it might look something like: type MapTuple<T> = { [K in keyof T]: T[K]["key"] } but this doesn't work. This question is the inverse of Typescript: object

问题 What are the types of the four parameters for the error handling function when coding in Typescript? app.use((err: ??, req: ??, res: ??, next: ??) => { }); I am using VS Code and no hints are offered. I get red wiggly lines under all four parameters. The error says "Parameter implicitly has 'any' type". Actually I am confused with this message. If it treats it as an any type, then isn't that a valid choice? 回答1: The function itself has the following signature (taken from DefinitelyTyped):

问题 I want to extend a class which does not exist at transpile time. It is only loaded runtime (global library). However, we got the type definitions ofthe library. Is there any other way than using any for the base class which doesn't have the advantages of typing? Example with following error message: Type 'A' is not a constructor function type. /* Some external library with typings. */ class A { constructor() { } } /* Factory to inject dependency which does not exist at transpile time, only at

问题 I have a given interface which comes from another package, so I can't really change it. For the sake of simplicity, let's just say the following interface: interface SomeInterface { someProp: string; someOtherProp?: number; } I was wondering if I can somehow extract the types of all properties so I would get a combined type which could be any of the original Interface's properties. In the example, it would resolve to a type being string | number | undefined . Also, not really the same

问题 I am just digging into Typescript typings and I wondered how to define a type which is a tuple but with unordered element types. I mean, having type SimpleTuple = [number, string]; const tup1: SimpleTuple = [7, `7`]; // Valid const tup2: SimpleTuple = [`7`, 7]; // 'string' is not assignable to 'number' // and vice-versa This is useful in many cases, but what if I don't care about order or I need it to be unordered. The example above is quite trivial since I could define type

问题 I am just digging into Typescript typings and I wondered how to define a type which is a tuple but with unordered element types. I mean, having type SimpleTuple = [number, string]; const tup1: SimpleTuple = [7, `7`]; // Valid const tup2: SimpleTuple = [`7`, 7]; // 'string' is not assignable to 'number' // and vice-versa This is useful in many cases, but what if I don't care about order or I need it to be unordered. The example above is quite trivial since I could define type

问题 I'm using winston 3.0 with the @types/winston types. These types are not yet fully compatible, and I've come across an error in the types which I don't know how to correct. Here's my code. logger.ts export function middleware(): express.Handler { const transport = new winston.transports.Console({ json: true, colorize: true, stringify: getStringify() }); const loggerOptions: expressWinston.LoggerOptionsWithTransports = { transports: [transport], meta: true, msg: "HTTP {{req.method}} {{req.url}