Skip to content

Commit 1b6c810

Browse files
Hkr32Hkr32
committed
Merge update
2 parents d831dbb + f469ceb commit 1b6c810

File tree

647 files changed

+25371
-18251
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

647 files changed

+25371
-18251
lines changed

‎.eslintignore‎

Lines changed: 0 additions & 3 deletions
This file was deleted.

‎.eslintrc.cjs‎

Lines changed: 0 additions & 243 deletions
This file was deleted.

‎.github/ISSUE_TEMPLATE/bug_report.yml‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ body:
1818
id: reproduction
1919
attributes:
2020
label: Reproduction
21-
description: Please provide a link via [vite.new](https://vite.new/) or a link to a repo that can reproduce the problem you ran into. `npm create vite@latest` and `npm create vite-extra@latest` (for SSR or library repros) can be used as a starter template. A [minimal reproduction](https://stackoverflow.com/help/minimal-reproducible-example) is required ([Why?](https://antfu.me/posts/why-reproductions-are-required)). If a report is vague (e.g. just a generic error message) and has no reproduction, it will receive a "need reproduction" label. If no reproduction is provided after 3 days, it will be auto-closed.
21+
description: Please provide a link via [vite.new](https://vite.new/) or a link to a repo that can reproduce the problem you ran into. `npm create vite@latest` and `npm create vite-extra@latest` (for SSR or library repros) can be used as a starter template. A [minimal reproduction](https://stackoverflow.com/help/minimal-reproducible-example) is required ([Why?](https://antfu.me/posts/why-reproductions-are-required)). If a report is vague (e.g. just a generic error message) and has no reproduction, it will receive a "needs reproduction" label. If no reproduction is provided after 3 days, it will be auto-closed.
2222
placeholder: Reproduction URL
2323
validations:
2424
required: true
@@ -46,6 +46,7 @@ body:
4646
- npm
4747
- yarn
4848
- pnpm
49+
- bun
4950
validations:
5051
required: true
5152
- type: textarea

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 9 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,14 @@
1-
<!-- Thank you for contributing! -->
2-
31
### Description
42

5-
<!-- Please insert your description here and provide especially info about the "what" this PR is solving -->
6-
7-
### Additional context
8-
9-
<!-- e.g. is there anything you'd like reviewers to focus on? -->
10-
11-
---
12-
13-
### What is the purpose of this pull request? <!-- (put an "X" next to an item) -->
3+
<!-- What is this PR solving? Write a clear description or reference the issues it solves (e.g. `fixes #123`). What other alternatives have you explored? Are there any parts you think require more attention from reviewers? -->
144

15-
- [ ] Bug fix
16-
- [ ] New Feature
17-
- [ ] Documentation update
18-
- [ ] Other
5+
<!----------------------------------------------------------------------
6+
Before creating the pull request, please make sure you do the following:
197
20-
### Before submitting the PR, please make sure you do the following
8+
- Read the Contributing Guidelines at https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md.
9+
- Check that there isn't already a PR that solves the problem the same way. If you find a duplicate, please help us reviewing it.
10+
- Update the corresponding documentation if needed.
11+
- Include relevant tests that fail without this PR but pass with it.
2112
22-
- [ ] Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md), especially the [Pull Request Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md#pull-request-guidelines).
23-
- [ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
24-
- [ ] Provide a description in this PR that addresses **what** the PR is solving, or reference the issue that it solves (e.g. `fixes #123`).
25-
- [ ] Update the corresponding documentation if needed.
26-
- [ ] Ideally, include relevant tests that fail without this PR but pass with it.
13+
Thank you for contributing to Vite!
14+
----------------------------------------------------------------------->

‎.github/issue-workflow-dark.png‎

-269 KB
Binary file not shown.

0 commit comments

Comments
 (0)