vue-server-renderer 2.1.8 on Node.js NPM

The transition behavior change introduced in 2.1.7 has been reverted. All transitions that worked in 2.1.6 and earlier should work exactly the same in 2.1.8.
In order to properly solve #4510, a new type of transition class (-to) is introduced. Now for each transition phase (enter, leave, appear) there are three classes. For example for a leaving transition:
- v-leave: the starting state for the transition;
- v-leave-to: the ending state for the transition;
- v-leave-active: applied across the entire transition duration.
Both v-leave and v-leave-active behave exactly like before. The only difference between v-leave-to and v-leave-active is that it is applied one frame after the transition starts.
The reason for this is that enter transitions are triggered by the removal of v-enter, which is also one frame after the transition starts. So using v-leave-to instead of v-leave-active ensures that enter and leave transitions triggered at the same time also start in the exact same frame. The class name also more correctly express what it represents.
All previous transition code will continue to work, but from now on it is recommended to use v-leave-to to indicate leaving transition end state.

#4545 fix dynamic transition type for higher-order transition components
#4560 fix hydration error when interpolated text contains CRLF
#4564, #4584, #4589 fix regression patch error for elements containing both components and <slot> (@defcc via #4572)
#4576 fix enter transition flicker regression
#4586 fix checkbox v-model checked state for non-boolean values