beforeDestroy is called in Vue 2 before the instance is destroyed and is used to clean up event listeners, timers, etc. 1. Run after all subcomponents have been destroyed; 2. The instance is still fully available at this time; 3. Suitable for manually cleaning content that Vue does not process automatically, such as global events, timers, WebSocket connections; 4. Unlike destroy, the latter is called after the component is completely destroyed; 5. Common uses include removing window event listening, clearing timers, and unsubscribing services; 6. Be careful not to add responsive attributes or performing time-consuming operations here, and make sure to cancel asynchronous tasks to avoid errors.
In Vue 2, the beforeDestroy
hook is called right before a Vue instance is destroyed. This happens after the instance is fully functional but just before it starts tearing everything down—like removing watchers, child components, and direct bindings.
This lifecycle stage gives you a chance to do any necessary cleanup, like removing event listeners or canceling async operations that might still be running.
When exactly does beforeDestroy run?
The beforeDestroy
lifecycle hook runs after :
- All child components have been destroyed.
- The Vue instance is still fully functional (you can still access data, methods, etc.).
It's the perfect time to manually clean up things that Vue doesn't automatically handle, such as:
- Event listeners added outside of Vue (eg, with
window.addEventListener
) - Timers (
setTimeout
,setInterval
) - WebSocket connections
- Any third-party libraries that need explicit teardown
At this point, the component is about to be torn down, so anything you want to remove or reset should be done here.
How is beforeDestroy different from destroyed?
Here's how these two hooks compare:
-
beforeDestroy
: Called just before destruction begins. Component is still active. -
destroyed
: Called after the component has been fully destroyed. Everything has been cleaned up by Vue.
Once you're in destroyed
, most of the component's internal systems are already gone. So if you need to reference component data or call methods, do it in beforeDestroy
.
Practical use cases for beforeDestroy
A few common scenarios where beforeDestroy
comes in handy:
-
Unbinding global events : If you added an event listener on
window
ordocument
, you should remove it here.beforeDestroy() { window.removeEventListener('resize', this.handleResize); }
Clearing times : Prevent memory leaks by clearing any pending timeouts or intervals.
beforeDestroy() { if (this.pollingTimer) { clearInterval(this.pollingTimer); } }
Cleaning up subscriptions : If you're using a pub/sub system or connecting to external services, make sure to unsubscribe or disconnect.
Things to keep in mind
- Don't add new reactive properties here — it won't work.
- Avoid doing heavy computings unless absolutely necessary.
- Make sure any async tasks (like API calls) are cancelled to prevent errors when trying to update a non-existent component.
Also, remember that once the instance is destroyed, it can't be reused. So if you're caching references or storing state elsewhere, now's the time to wrap that up cleanly.
Basically that's it.
The above is the detailed content of When is the beforeDestroy hook called in Vue 2?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

HeadlessUIinVue refers to a library of UI components that provide no preset styles and only contains core logic and behavior. Its features include: 1. No style restrictions, developers can customize the design; 2. Focus on barrier-free and interactive logic, such as keyboard navigation, state management, etc.; 3. Support Vue framework integration, exposing the control interface through combinable functions or components. Reasons for use include: maintaining design consistency, built-in accessibility, strong component reusability, and lightweight library size. In practical applications, developers need to write HTML and CSS themselves. For example, when building a drop-down menu, the library handles state and interaction, while developers decide on visual presentation. Mainstream libraries include HeadlessUI and RadixVue for TailwindLabs, suitable for

In Vue3, there are three ways to monitor nested properties using the watch function: 1. Use the getter function to accurately monitor specific nested paths, such as watch(()=>someObject.nested.property,callback); 2. Add the {deep:true} option to deeply monitor changes within the entire object, which is suitable for situations where the structure is complex and does not care about which property changes; 3. Return an array in the getter to listen to multiple nested values ??at the same time, which can be used in combination with deep:true; in addition, if ref is used, the nested properties in its .value need to be tracked through getter.

Building a Vue component library requires designing the structure around the business scenario and following the complete process of development, testing and release. 1. The structural design should be classified according to functional modules, including basic components, layout components and business components; 2. Use SCSS or CSS variables to unify the theme and style; 3. Unify the naming specifications and introduce ESLint and Prettier to ensure the consistent code style; 4. Display the usage of components on the supporting document site; 5. Use Vite and other tools to package as NPM packages and configure rollupOptions; 6. Follow the semver specification to manage versions and changelogs when publishing.

Vue3 has improved in many key aspects compared to Vue2. 1.Composition API provides a more flexible logical organization method, allowing centralized management of related logic, while still supporting Vue2's Options API; 2. Better performance and smaller package size, the core library is reduced by about 30%, the rendering speed is faster and supports better tree shake optimization; 3. The responsive system uses ES6Proxy to solve the problem of unable to automatically track attribute addition and deletion in Vue2, making the responsive mechanism more natural and consistent; 4. Built-in better support for TypeScript, support multiple node fragments and custom renderer API, improving flexibility and future adaptability. Overall, Vue3 is a smooth upgrade to Vue2,

? in regular expressions are used to convert greedy matches to non-greedy, achieving more accurate matches. 1. It makes the content as little as possible to match as little as possible to avoid mismatch across tags or fields; 2. It is often used in scenarios such as HTML parsing, log analysis, URL extraction, etc. that require precise control of the scope; 3. When using it, it is necessary to note that not all quantifiers are applicable. Some tools need to manually enable non-greedy mode, and complex structures need to be combined with grouping and assertions to ensure accuracy. Mastering this technique can significantly improve text processing efficiency.

This article has selected a series of top-level finished product resource websites for Vue developers and learners. Through these platforms, you can browse, learn, and even reuse massive high-quality Vue complete projects online for free, thereby quickly improving your development skills and project practice capabilities.

CORSissuesinVueoccurduetothebrowser'ssame-originpolicywhenthefrontendandbackenddomainsdiffer.Duringdevelopment,configureaproxyinvue.config.jstoredirectAPIrequeststhroughthedevserver.Inproduction,ensurethebackendsetsproperCORSheaders,allowingspecifico

Deploying Vue applications to production environments requires optimization of performance, ensuring stability and improving loading speed. 1. Use VueCLI or Vite to build a production version, generate a dist directory and set the correct environment variables; 2. If you use VueRouter's history mode, you need to configure the server to fallback to index.html; 3. Deploy the dist directory to Nginx/Apache, Netlify/Vercel or combine CDN acceleration; 4. Enable Gzip compression and browser caching strategies to optimize loading; 5. Implement lazy loading components, introduce UI libraries on demand, enable HTTPS, prevent XSS attacks, add CSP headers, and restrict third-party SDK domain names to enhance security.
