You just have to specify the aliases in your vitest.config.js file: import path from ‘path’ import vue from ‘@vitejs/plugin-vue’ export default { plugins: [vue()], test: { globals: true, environment: ‘jsdom’, }, resolve: { alias: { ‘@’: path.resolve(__dirname, ‘./src’) }, }, }
This has changed with TypeScript 0.8.2. You now change TypeScriptTarget in the .csproj file from: <TypeScriptTarget>ES3</TypeScriptTarget> to <TypeScriptTarget>ES5</TypeScriptTarget> MyApp.csproj: <PropertyGroup Condition=”‘$(Configuration)’ == ‘Debug'”> <TypeScriptTarget>ES5</TypeScriptTarget> <TypeScriptIncludeComments>true</TypeScriptIncludeComments> <TypeScriptSourceMap>true</TypeScriptSourceMap> <TypeScriptModuleKind>AMD</TypeScriptModuleKind> </PropertyGroup> <PropertyGroup Condition=”‘$(Configuration)’ == ‘Release'”> <TypeScriptTarget>ES5</TypeScriptTarget> <TypeScriptIncludeComments>false</TypeScriptIncludeComments> <TypeScriptSourceMap>false</TypeScriptSourceMap> <TypeScriptModuleKind>AMD</TypeScriptModuleKind> </PropertyGroup> See also Asher Barak answer
Problem is here Element, document, and window can be an EventTarget. You should detect your EventTarget if is an element. So in your case below code should work linkProvider = (ev: React.SyntheticEvent<EventTarget>) => { // If event target not an HTMLButtonElement, exit if (!(ev.target instanceof HTMLButtonElement)) { return; } console.debug(‘ev.target’, ev.target.dataset[‘ix’]) } In the short … Read more
Here is an easy and naive implementation of what you’re asking for: interface IDataNode { id: number; title: string; node: Array<IDataNode>; } If you want to instantiate said nodes from code: class DataNode implements IDataNode { id: number; title: string; node: Array<IDataNode>; constructor(id: number, title: string, node?: Array<IDataNode>) { this.id = id; this.title = title; … Read more
I had a similar issue where I was using async\await and Promises (both ES6 constructs) using the import keyword in the ts source files to import other ts modules. I could transpile with TypeScript using the default js target version (ES5) which produces transpile errors complaining about the async\await and Promise keywords but since I’m … Read more
As some of the comments indicated, your this reference is not typed because you are using the function () {} syntax to define your function. The this object inside such a function will inherently be of type any , because this will be the caller of the function (unknowable at design-time). If you change your … Read more
Perhaps you are thinking of something like this? interface FunctionInterface { (s: string): boolean; } const f: FunctionInterface = s => true; const b: boolean = f(‘someString’);
The only possible way this could work at compile time is if your arrays are tuples composed of literals. For example, here are some arrays with the same runtime values, but with different types in TypeScript: const tupleOfLiterals: [1, 2, 2] = [1, 2, 2]; const tupleOfNonLiterals: [number, number, number] = [1, 2, 2]; const … Read more
One way of doing it, which is a bit annoying, is creating a declaration file with the same name. component – component.d.ts <— – component.android.tsx – component.ios.tsx then import { file } from “../group/file”; Update: Another way of doing it is just omit the extension for one of them, then typescript will pick up the … Read more
This is what I’ve ended up doing to type the getInitialProps and render methods: import React, { ReactElement } from “react”; import Document, { DocumentInitialProps, DocumentContext } from ‘next/document’; export default class MyDocument extends Document { static async getInitialProps(ctx: DocumentContext): Promise<DocumentInitialProps> { // … } render(): ReactElement { return( // … ); } } https://github.com/vercel/next.js/blob/canary/examples/with-styled-components/pages/_document.js … Read more