Please enable JavaScript.

Coggle requires JavaScript to display documents.

vue (vue router (memo (nested route (name view (using the help vue know…

- - - - point out the path (quite verbose and repeative)
    - - specify the place the matched component will be rendered
    - - get the params path in every shared components
    - - still using <router-view> in the parent component - place you want it render the nested component
      - in the router property in app instance inside the paticular path we using children property to keep nesting the router.
      - name view
        
        using the help vue know which component you want to render
    - - navigation the route by coding
        
        <router-link :to="..."> same router.push(...)
        
        :forbidden: cannot use path + params
        
        :check: can use name + params (name is brother with the path property)
        
        query
      - router.go
- - - - data and event is not ready yet.
    - - data and event is observed. but not mount to DOM yet.
    - - template has compiled. virtual DOM has update. ready to mount
    - - $el is available in this time
      - $el === document.getelement..
    - - chỉ gọi khi nào component đã mounted và có sử thay đổi
      - nếu component chưa mounted thì hàm sẽ không có gọi dù có sửj thay đôir hay không
  - - - performance cost high. force the user pc must download all of components before it render
      - using Vue.Component
    - - good for performance
      - not using Vue.component but use components property
- - - - nuxt.js
        
        the tool make everything as boilplate. help you to save the time
      - vue-server-renderer :red_flag:
    - - life cycle hook
        
        cannot use mounted beforemount destroy ect
        
        setinterval should call in the mounted . so ther client-side can destroy it
      - custom directive
        
        manipulate the DOM so it cannot happen as server rendering.
    - - Don’t call browser-specific APIs in created or beforeCreate
  - - - https://www.netlify.com/blog/2016/11/22/prerendering-explained/
      - https://www.thomas-sulzbach.de/2018/04/04/understanding-prerendering-with-vue-js-and-prerender-spa-plugin/
        
        notice that the if you use transition components and use prerender then the bot still read the opacity 0
- - - - cached the components