.github/ISSUE_TEMPLATE/bug_report.yml

@@ -78,13 +78,13 @@ body:
           required: true
         - label: Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
           required: true
-        - label: Read the [docs](https://vitejs.dev/guide).
+        - label: Read the [docs](https://vite.dev/guide).
           required: true
         - label: Check that there isn't [already an issue](https://github.com/vitejs/vite/issues) that reports the same bug to avoid creating a duplicate.
           required: true
         - label: 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](https://github.com/vuejs/core) instead.
           required: true
-        - label: Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitejs/vite/discussions) or join our [Discord Chat Server](https://chat.vitejs.dev/).
+        - label: Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitejs/vite/discussions) or join our [Discord Chat Server](https://chat.vite.dev/).
           required: true
         - label: The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.
           required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -7,7 +7,7 @@ contact_links:
     url: https://github.com/vitejs/vite-plugin-vue/issues/new/choose
     about: Vue related issues should be reported on the vite-plugin-vue repository.
   - name: Discord Chat
-    url: https://chat.vitejs.dev
+    url: https://chat.vite.dev
     about: Ask questions and discuss with other Vite users in real time.
   - name: Questions & Discussions
     url: https://github.com/vitejs/vite/discussions

.github/ISSUE_TEMPLATE/docs.yml

@@ -1,5 +1,5 @@
 name: "\U0001F4DA Documentation"
-description: Suggest a change or new page to be added to vitejs.dev
+description: Suggest a change or new page to be added to vite.dev
 labels: [documentation]
 body:
   - type: markdown

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -41,7 +41,7 @@ body:
           required: true
         - label: Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
           required: true
-        - label: Read the [docs](https://vitejs.dev/guide).
+        - label: Read the [docs](https://vite.dev/guide).
           required: true
         - label: Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
           required: true

.github/renovate.json5

@@ -17,6 +17,8 @@
     "node",
     "typescript",
     "eslint-plugin-react-hooks", // prevent bumping to messy -rc-<hash>-<date>
+    "@rollup/plugin-dynamic-import-vars", // prefer version using tinyglobby
+    "@types/express", // express latest is still on v4, so types should also be v4
 
     // pinned
     "slash3",

.github/workflows/ci.yml

@@ -48,7 +48,7 @@ jobs:
 
       - name: Get changed files
         id: changed-files
-        uses: tj-actions/changed-files@e9772d140489982e0e3704fea5ee93d536f1e275 # v45.0.1
+        uses: tj-actions/changed-files@4edd678ac3f81e2dc578756871e4d00c19191daf # v45.0.4
         with:
           files: |
             docs/**
@@ -69,9 +69,9 @@ jobs:
         include:
           # Active LTS + other OS
           - os: macos-latest
-            node_version: 20
+            node_version: 22
           - os: windows-latest
-            node_version: 20
+            node_version: 22
       fail-fast: false
 
     name: "Build&Test: node-${{ matrix.node_version }}, ${{ matrix.os }}"
@@ -129,6 +129,22 @@ jobs:
       - name: Test build
         run: pnpm run test-build
 
+  test-passed:
+    if: (!cancelled() && !failure())
+    needs: test
+    runs-on: ubuntu-latest
+    name: Build & Test Passed or Skipped
+    steps:
+      - run: echo "Build & Test Passed or Skipped"
+
+  test-failed:
+    if: (!cancelled() && failure())
+    needs: test
+    runs-on: ubuntu-latest
+    name: Build & Test Failed
+    steps:
+      - run: echo "Build & Test Failed"
+
   lint:
     timeout-minutes: 10
     runs-on: ubuntu-latest
@@ -155,7 +171,7 @@ jobs:
         run: pnpm run lint
 
       - name: Check formatting
-        run: pnpm prettier --check .
+        run: pnpm prettier --write --log-level=warn . && git diff --exit-code
 
       - name: Typecheck
         run: pnpm run typecheck

.github/workflows/lock-closed-issues.yml

@@ -19,6 +19,6 @@ jobs:
           #issue-comment: |
           #  This issue has been locked since it has been closed for more than 14 days.
           #
-          #  If you have found a concrete bug or regression related to it, please open a new [bug report](https://github.com/vitejs/vite/issues/new/choose) with a reproduction against the latest Vite version. If you have any other comments you should join the chat at [Vite Land](https://chat.vitejs.dev) or create a new [discussion](https://github.com/vitejs/vite/discussions).
+          #  If you have found a concrete bug or regression related to it, please open a new [bug report](https://github.com/vitejs/vite/issues/new/choose) with a reproduction against the latest Vite version. If you have any other comments you should join the chat at [Vite Land](https://chat.vite.dev) or create a new [discussion](https://github.com/vitejs/vite/discussions).
           issue-lock-reason: ""
           process-only: "issues"

.github/workflows/preview-release.yml

@@ -0,0 +1,38 @@
+name: Preview release
+
+env:
+  # install playwright binary manually (because pnpm only runs install script once)
+  PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD: "1"
+
+permissions:
+  pull-requests: write
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types: [opened, synchronize, labeled]
+
+jobs:
+  preview:
+    if: >
+      github.repository == 'vitejs/vite' &&
+      (github.event_name == 'push' ||
+      (github.event_name == 'pull_request' && contains(github.event.pull_request.labels.*.name, 'trigger: preview')))
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4.0.0
+
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Build
+        working-directory: ./packages/vite
+        run: pnpm build
+
+      - run: pnpm dlx pkg-pr-new@0.0 publish --compact --pnpm ./packages/vite

.npmrc

@@ -1,4 +1,3 @@
-hoist-pattern[]=ts-node # package/vite: postcss-load-config
 hoist-pattern[]=postcss # package/vite
 hoist-pattern[]=pug # playground/tailwind: @vue/compiler-sfc
 shell-emulator=true

.prettierignore

@@ -1,5 +1,6 @@
 packages/*/CHANGELOG.md
 packages/vite/src/node/ssr/runtime/__tests__/fixtures
+packages/vite/src/node/ssr/__tests__/fixtures/errors
 playground-temp/
 dist/
 temp/

CODE_OF_CONDUCT.md

@@ -34,7 +34,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team by DM at [Vite Land](https://chat.vitejs.dev). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team by DM at [Vite Land](https://chat.vite.dev). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Vite Contributing Guide
 
-Hi! We're really excited that you're interested in contributing to Vite! Before submitting your contribution, please read through the following guide. We also suggest you read the [Project Philosophy](https://vitejs.dev/guide/philosophy) in our documentation.
+Hi! We're really excited that you're interested in contributing to Vite! Before submitting your contribution, please read through the following guide. We also suggest you read the [Project Philosophy](https://vite.dev/guide/philosophy) in our documentation.
 
 You can use [StackBlitz Codeflow](https://stackblitz.com/codeflow) to fix bugs or implement features. You'll see a Codeflow button on issues to start a PR to fix them. A button will also appear on PRs to review them without needing to check out the branch locally. When using Codeflow, the Vite repository will be cloned for you in an online editor, with the Vite package built in watch mode ready to test your changes. If you'd like to learn more, check out the [Codeflow docs](https://developer.stackblitz.com/codeflow/what-is-codeflow).
 
@@ -207,42 +207,80 @@ You can set the `--debug` option to turn on debugging logs (e.g. `vite --debug r
 
 ```mermaid
 flowchart TD
-    start{Followed issue\ntemplate?}
-    start --NO--> close1[Close and ask to\nfollow template]
+    start{Followed issue
+        template?}
+    start --NO--> close1["Close and ask to
+        follow template"]
     start --YES--> dupe{Is duplicate?}
-    dupe --YES--> close2[Close and point\nto duplicate]
-    dupe --NO--> repro{Has proper\nreproduction?}
-    repro --NO--> close3[Label: 'needs reproduction'\nbot will auto close if no update\nhas been made in 3 days]
+    dupe --YES--> close2[Close and point
+        to duplicate]
+    dupe --NO--> repro{Has proper
+      reproduction?}
+    repro --NO--> close3[Label: 'needs reproduction'
+        bot will auto close if no update
+        has been made in 3 days]
     repro --YES--> real{Is actually a bug?}
-    real --NO--> intended{Is the intended\nbehaviour?}
-    intended --YES--> explain[Explain and close\npoint to docs if needed]
-    intended --NO--> open[Keep open for discussion\nRemove 'pending triage' label]
-    real --YES--> real2["1. Remove 'pending triage' label\n2. Add related feature label if\napplicable (e.g. 'feat: ssr')\n3. Add priority and meta labels (see below)"]
-    real2 --> unusable{Does the\nbug make Vite\nunusable?}
-    unusable --YES--> maj{Does the bug\naffect the majority\nof Vite users?}
+    real --NO--> intended{Is the intended
+        behaviour?}
+    intended --YES--> explain[Explain and close
+        point to docs if needed]
+    intended --NO--> open[Keep open for discussion
+        Remove 'pending triage' label]
+    real --YES--> real2["① Remove 'pending triage' label
+        ② Add related feature label if applicable
+        (e.g. 'feat: ssr')
+        ③ Add priority and meta labels (see below)"]
+    real2 --> unusable{Does the
+        bug make Vite
+        unusable?}
+    unusable --YES--> maj{Does the bug
+        affect the majority
+        of Vite users?}
     maj --YES--> p5[p5: urgent]
     maj --NO--> p4[p4: important]
-    unusable --NO--> workarounds{Are there\nworkarounds for\nthe bug?}
+    unusable --NO--> workarounds{Are there
+        workarounds for
+        the bug?}
     workarounds --NO--> p3[p3: minor bug]
-    workarounds --YES--> p2[p2: edge case\nhas workaround]
+    workarounds --YES--> p2[p2: edge case
+        has workaround]
 ```
 
 ### Pull Request Review Workflow
 
 ```mermaid
 flowchart TD
-    start{Bug fix\nor\nfeature}
-    start --BUG FIX--> strict_bug{"Is this a 'strict fix'?\ni.e. fixes an obvious\noversight with no\nside effects"}
-    start --FEATURE--> feature[- Discuss feature necessity\n- Is there a better way\nto address the need?\n- Review code quality\n- Add labels\n- Add to milestone\n- Add to Team Board]
-    feature -.-> approve_non_strict[- Run vite-ecosystem-ci if needed\n- Approve if you feel strongly\nthat the PR is needed\nand add to milestone]
-    strict_bug --YES--> strict[- Verify the fix locally\n- Review code quality\n- Require test case if applicable\n- Request changes if necessary\n- Add labels]
-    strict_bug --NO--> non_strict[Discuss the potential side\neffects of the fix, e.g.\n- Could it introduce implicit\nbehavior changes in other cases?\n- Does it introduce too much changes?\n- Add labels\n- Add to Team Board]
+    start{Bug fix
+        or
+        feature}
+    start --BUG FIX--> strict_bug{"Is this a 'strict fix'?
+        i.e. fixes an obvious oversight with no side effects"}
+    start --FEATURE--> feature[• Discuss feature necessity
+        • Is there a better way to address the need?
+        • Review code quality
+        • Add labels
+        • Add to milestone
+        • Add to Team Board]
+    feature -.-> approve_non_strict[• Run vite-ecosystem-ci if needed
+        • Approve if you feel strongly that the PR is needed and add to milestone]
+    strict_bug --YES--> strict[• Verify the fix locally
+        • Review code quality
+        • Require test case if applicable
+        • Request changes if necessary
+        • Add labels]
+    strict_bug --NO--> non_strict[Discuss the potential side effects of the fix, e.g.
+        • Could it introduce implicit behavior changes in other cases?
+        • Does it introduce too much changes?
+        • Add labels
+        • Add to Team Board]
     non_strict -.-> approve_non_strict
     strict --> approve_strict[Approve if ready to be merged]
-    approve_strict --> merge_strict[Merge if approved by 2 or\nmore team members]
-    approve_non_strict -.-> merge_non_strict[Merge if approved by 2 or\nmore team members\nand the PR has been discussed\n in a team meeting]
+    approve_strict --> merge_strict[Merge if approved by 2 or more team members]
+    approve_non_strict -.-> merge_non_strict[Merge if approved by 2 or more team members and the PR has been discussed in a team meeting]
     merge_non_strict -.-> merge_extra
-    merge_strict --> merge_extra["- Use 'Squash and Merge'\n- Edit commit message to follow convention\n- In commit message body, list\nrelevant issues being fixed\ne.g. 'fix #1234, fix #1235'"]
+    merge_strict --> merge_extra["• Use 'Squash and Merge'
+        • Edit commit message to follow convention
+        • In commit message body, list relevant issues being fixed e.g. 'fix #1234, fix #1235'"]
 ```
 
 ## Notes on Dependencies

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2019-present, Yuxi (Evan) You and Vite contributors
+Copyright (c) 2019-present, VoidZero Inc. and Vite contributors
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,6 +1,6 @@
 <p align="center">
-  <a href="https://vitejs.dev" target="_blank" rel="noopener noreferrer">
-    <img width="180" src="https://vitejs.dev/logo.svg" alt="Vite logo">
+  <a href="https://vite.dev" target="_blank" rel="noopener noreferrer">
+    <img width="180" src="https://vite.dev/logo.svg" alt="Vite logo">
   </a>
 </p>
 <br/>
@@ -9,7 +9,7 @@
   <a href="https://nodejs.org/en/about/previous-releases"><img src="https://img.shields.io/node/v/vite.svg" alt="node compatibility"></a>
   <a href="https://github.com/vitejs/vite/actions/workflows/ci.yml"><img src="https://github.com/vitejs/vite/actions/workflows/ci.yml/badge.svg?branch=main" alt="build status"></a>
   <a href="https://pr.new/vitejs/vite"><img src="https://developer.stackblitz.com/img/start_pr_dark_small.svg" alt="Start new PR in StackBlitz Codeflow"></a>
-  <a href="https://chat.vitejs.dev"><img src="https://img.shields.io/badge/chat-discord-blue?style=flat&logo=discord" alt="discord chat"></a>
+  <a href="https://chat.vite.dev"><img src="https://img.shields.io/badge/chat-discord-blue?style=flat&logo=discord" alt="discord chat"></a>
 </p>
 <br/>
 
@@ -26,13 +26,13 @@
 
 Vite (French word for "quick", pronounced [`/vit/`](https://cdn.jsdelivr.net/gh/vitejs/vite@main/docs/public/vite.mp3), like "veet") is a new breed of frontend build tooling that significantly improves the frontend development experience. It consists of two major parts:
 
-- A dev server that serves your source files over [native ES modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules), with [rich built-in features](https://vitejs.dev/guide/features.html) and astonishingly fast [Hot Module Replacement (HMR)](https://vitejs.dev/guide/features.html#hot-module-replacement).
+- A dev server that serves your source files over [native ES modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules), with [rich built-in features](https://vite.dev/guide/features.html) and astonishingly fast [Hot Module Replacement (HMR)](https://vite.dev/guide/features.html#hot-module-replacement).
 
-- A [build command](https://vitejs.dev/guide/build.html) that bundles your code with [Rollup](https://rollupjs.org), pre-configured to output highly optimized static assets for production.
+- A [build command](https://vite.dev/guide/build.html) that bundles your code with [Rollup](https://rollupjs.org), pre-configured to output highly optimized static assets for production.
 
-In addition, Vite is highly extensible via its [Plugin API](https://vitejs.dev/guide/api-plugin.html) and [JavaScript API](https://vitejs.dev/guide/api-javascript.html) with full typing support.
+In addition, Vite is highly extensible via its [Plugin API](https://vite.dev/guide/api-plugin.html) and [JavaScript API](https://vite.dev/guide/api-javascript.html) with full typing support.
 
-[Read the Docs to Learn More](https://vitejs.dev).
+[Read the Docs to Learn More](https://vite.dev).
 
 ## Packages