VulnPulse

Vue.js Blogの情報

9月1日(日)

  • Announcing Vue 3.5

    Today we are excited to announce the release of Vue 3.5 "Tengen Toppa Gurren Lagann"! This minor release contains no breaking changes and includes both internal improvements and useful new features. We will cover some highlights in this blog post - for a full list of changes and new features, please consult the full changelog on GitHub .

3月21日(木)

  • Announcing VitePress 1.0

    Today we are happy to announce the (long overdue) 1.0 release of VitePress ! VitePress is a Static Site Generator (SSG) designed for building fast, content-centric websites. In a nutshell, VitePress takes your source content written in Markdown, applies a theme to it, and generates static HTML pages that can be easily deployed anywhere. VitePress is built on top of Vite and Vue , and is the spiritual successor and modern replacement of VuePress .

12月28日(木)

  • Announcing Vue 3.4

    Today we're excited to announce the release of Vue 3.4 "🏀 Slam Dunk"! This release includes some substantial internal improvements - most notably a rewritten template parser that is 2x faster, and a refactored reactivity system that makes effect triggering more accurate and efficient. It also packs a number of quality-of-life API improvements, including the stabilization of defineModel and a new same-name shorthand when binding props. This post provides an overview of the highlighted features in 3.4. For the full list of changes, please consult the full changelog on GitHub .

12月15日(金)

  • Vue 2 is Approaching End Of Life

    With 2024 almost upon us, we would like to take this opportunity to remind the Vue community that Vue 2 will reach End of Life (EOL) on December 31st, 2023. Vue 2.0 was released more than 7 years ago in 2016. It was a major milestone in Vue's journey of becoming a mainstream framework. Many current Vue users started using Vue during the Vue 2 era, and many great things have been built with it. However, active maintenance of two major versions in parallel isn't sustainable for us. As Vue 3 and its ecosystem have matured, it is time for the team to move on and focus our energy on the latest maj…

5月11日(木)

  • Announcing Vue 3.3

    Today we're excited to announce the release of Vue 3.3 "Rurouni Kenshin"! This release is focused on developer experience improvements - in particular, SFC <script setup> usage with TypeScript. Together with the 1.6 release of Vue Language Tools (previously known as Volar), we have resolved many long-standing pain points when using Vue with TypeScript. This post provides an overview of the highlighted features in 3.3. For the full list of changes, please consult the full changelog on GitHub .

2月8日(水)

  • Volar: a New Beginning

    Most users of Volar know it as the official Vue.js VSCode extension. It started as a personal project when the official recommendation was still Vetur, and over time got adopted as the new official extension due to improved architecture and performance. As a project created to improve the quality of life for developers, we spent over two years before reaching 1.0 , and have been continuously shipping stability improvements. But we've still got more work to do, and there are exciting plans for 2023.

1月1日(日)

12月5日(月)

10月10日(月)

  • Volar 1.0 "Nika" Released!

    We are happy to announce that we have released v1.0 of Volar, the official IDE/TS tooling support for Vue! 🎉 This major version ships with tons of improvements across the board. In addition to improving UX, performance, and package size, we also released Plugin API v1 and refactored the core code to be framework-agnostic. 注:結尾附有中文版本 (There is Chinese version of this post at the end)。

7月1日(金)

6月20日(月)

1月20日(木)

8月5日(木)

1月11日(月)

9月18日(金)

  • Announcing Vue 3.0 "One Piece"

    Today we are proud to announce the official release of Vue.js 3.0 "One Piece". This new major version of the framework provides improved performance, smaller bundle sizes, better TypeScript integration, new APIs for tackling large scale use cases, and a solid foundation for long-term future iterations of the framework.