5 of 6 standards met
Summary inherits all augmented properties from the global interface. When consumers use with libraries that augment (e.g. , Expo, React Native), TypeScript raises conflicts: The is unnecessary โ the interface already explicitly declares all needed properties (, , ) and has as a catch-all for any additional properties (, , , , ). Changes : Remove from : Simplify to and remove the now-unnecessary comment โ is no longer inherited from 's augmentation Why this is safe The index signature already accepts any additional properties at runtime and set extra properties (, , , , ) via the index signature โ no inheritance needed ( with ) passes because without augmentations is , so was already a no-op in that context All 5 typecheck projects pass, full build passes, ESLint passes
Repository: vitejs/vite. Description: Next generation frontend tooling. It's fast! Stars: 78610, Forks: 7879. Primary language: TypeScript. Languages: TypeScript (82%), JavaScript (9.8%), HTML (4.8%), CSS (2.9%), Vue (0.2%). License: MIT. Homepage: http://vite.dev Topics: build-tool, dev-server, frontend, hmr, vite. Latest release: create-vite@8.3.0 (3w ago). Open PRs: 100, open issues: 534. Last activity: 5h ago. Community health: 87%. Top contributors: yyx990803, sapphi-red, patak-cat, bluwy, renovate[bot], antfu, btea, underfin, hi-ogawa, poyoho and others.
TypeScript
Last 12 weeks ยท 225 commits
Description Currently, Vite determines the default as: (default) when a file is present However, some environments can create a directory without a . For example, Deno projects using in generate and use a directory for dependency resolution. In this situation, Vite still falls back to , even though exists and could be used for caching. Suggested solution If a directory exists in the project root, Vite could default to: even when is not present. Alternative Workaround Currently this can be solved by explicitly setting: I ran into this when switching a project from Node.js to Deno so I could directly use without having to wait for the next major Node.js version. After the switch, Vite started creating a folder in the project root instead of using , which was confusing at first. It works fine once is configured manually, but it would be nice if this behaved the same way across environments when a directory is present. Additional context _No response_ Validations [x] Follow our Code of Conduct [x] Read the Contributing Guidelines. [x] Read the docs. [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
Describe the bug I tried to scaffold a new Tanstack route app both with beta and with vite 7, and it failed to create the app Reproduction https://github.com/vitejs/vite Steps to reproduce run bun create vite for Project Name: you can pick the current directory or give some name Select a framework: React Select a variant: TanStack Router โ https://tanstack.com/router Use Vite 8 beta (Experimental)?: Yes/No System Info Used Package Manager bun Logs error: too many arguments for 'create'. Expected 1 argument but got 4. Validations [x] Follow our Code of Conduct [x] Read the Contributing Guidelines. [x] Read the docs. [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead. [x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. [x] The provided reproduction is a minimal reproducible example of the bug.