5 of 6 standards met
Summary Adds support for .env files provided via Unix FIFOs (named pipes). Rationale 1Password recently launched local .env file support, which allows developers to securely access secrets stored in 1Password Environments via a local .env file that is actually a UNIX named pipe (FIFO). This lets secrets be streamed directly into processes without ever writing plaintext credentials to disk. Currently, Vite cannot read such mounted .env files because it only recognizes regular files using . This PR adds native FIFO (named pipe) support so that developers can seamlessly use Vite with 1Password's new .env destinations. This change brings Vite's .env file handling in line with other tools that support FIFOs, improving the developer experience for teams using 1Password Environments. Changes Modified to check for both regular files (isFile()) and FIFOs (isFIFO()) when loading environment files No behavioral change for regular .env files - existing functionality is preserved Tests Added test cases in : Notes Unix/macOS only (Windows named pipes not covered) FIFOs work the same as regular files from Vite's perspective - fs.readFileSync() handles FIFOs correctly
Repository: vitejs/vite. Description: Next generation frontend tooling. It's fast! Stars: 78485, Forks: 7863. Primary language: TypeScript. Languages: TypeScript (82.1%), JavaScript (9.7%), 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 (2w ago). Open PRs: 100, open issues: 532. Last activity: 12h 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 · 229 commits
Description This is the most popular place Suggested solution This is the most important part Alternative Support and proses earnings money to get the updated Additional context The best interest way 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.