Timothy Lau is Contributing…
close #4166
- I have read the contribution documentation for this project.
- I agree to follow the code of conduct that this project follows, as appropriate.
- The changes are appropriately documented (if applicable).
- The changes have sufficient test coverage (if applicable).
- The testsuite passes successfully on my local machine (if applicable).
Summary
This PR updates @electron-forge/plugin-vite to support Vite 8.
Electron Forge next currently uses Vite 7, while Vite 8 has already been released. This change updates the plugin so projects using Electron Forge can adopt the latest Vite version.
Changes
- update Vite dependency to v8
- adjust code to handle breaking changes between Vite 7 → Vite 8
- ensure the plugin continues to work with the current Electron Forge build pipeline
Testing
Tested with a local Electron Forge project using @electron-forge/plugin-vite and Vite 8.
Build, dev server, and renderer reload all work as expected.
Summary
This PR addresses a pending TODO comment left in #34499
This change removes the temporary workaround and replaces it with <Activity>, as originally intended.
How did you test this change?
- Updated the component to use
<Activity>directly - Verified the editor renders correctly in both development and production builds.
- The
<Activity>UI updates as expected.
Arc.mp4
close #8674
close #145
Downstream Issue: electron-userland/electron-builder#8674
: )
Although the JavaScript engine can handle this situation, attempting to handle both resolve and reject for the same Promise in the code logic indicates that the code structure is not sufficiently rigorous and may have design flaws. This can obscure the intent of the code and potentially confuse other developers.
EAvailableFeatures.guestCaProduction -> EAvailableFeatures.guestCamProduction
close #3783
Usages
actions:
- theme: brand
text: lorem ipsum
link: https://test.com
startIcon:
src: /test.svg
alt: test
width: 18
height: 18
or
actions:
- theme: brand
text: lorem ipsum
link: https://test.com
endIcon: <svg xmlns="http://www.w3.org/2000/svg" width="1em" height="1em" viewBox="0 0 24 24"><path fill="currentColor" d="m16.172 11l-5.364-5.364l1.414-1.414L20 12l-7.778 7.778l-1.414-1.414L16.172 13H4v-2z"/></svg>
About Docs
interface HeroAction {
// .....
// Show the left icon on action button.
startIcon?: ActionIcon
// Show the right icon on action button.
endIcon?: ActionIcon
}
type ActionIcon =
| string
| { src: string; alt?: string; width?: string; height: string }
| {
light: string
dark: string
alt?: string
width?: string
height: string
}ScreenShot

dart -> dark
close #3658
After multiple attempts to build the old version, I ultimately attributed the issue to the pull request in #3359.
I think it's a problem with VPLocalNavOutlineDropdown, because after deleting it in the VPLocalNav.vue file, this issue was resolved.
To delve deeper, it is the problem caused by onClickOutside of the @vueuse/core.
close #3641
If the configuration directory of VitePress is outside the project root directory, the project will not run correctly, so add this validation logic to ensure that the path entered by the user is within the root directory.
close #3622
It looks like a bug in #3622.
According to the docs about createContentLoader, the glob pattern should be relatived to the source directory instead of project root.
完成视频封面显示观看人数的实现
允许自定义Toc.vue的标题
新增疑难解答板块;
更新V1.0.2的更新日志;
liteflowx特别鸣谢的头像本地缓存;
新增1.0.1更新日志
解决公告框重复弹出问题;
新增不再提示功能;
pucKeyData、dwKeyLength参数应该包括结束符'\0'。
Last fetched:

