Router Transition not updates DOM unless refreshed

I am using vue 2.0.1 and router 2.0.0. I installed webpack template via cli following This link. The problem is when I click a link, the view does not update or change but the address bar shows change in route. Then I refresh the page and DOM gets updated and hence shows the component as expected but again If I click to the previous link, same problem follows with same solution i.e. refresh.

Here is my setup!

// sidebar.vue

<template lang="html">
  <aside class="menu" style="padding:10px 0 0 15px;">

  <ul class="menu-list">
    <li><router-link to="/">Dashboard</a></li>
    <li><router-link to="/customers">Customers</router-link></li>
  </ul>
</aside>
</template>

//router.js

import Vue from 'vue'
import VueRouter from 'vue-router'

import Right from './Right'
import Customers from './Customers'


Vue.use(VueRouter)

const routes = [
  { path: '/', component: Right },
  { path: '/customers', component: Customers }
]
const router = new VueRouter({
  routes // short for routes: routes
})

export default router

// App.vue

<template>
  <div class="columns">

      <sidebar></sidebar>

      <router-view class="view"></router-view>

  </div>
</template>

<script>
import router from './components/router.js'
import Sidebar from './components/Sidebar.vue'

export default {
  router,
  components: {
    Sidebar
  }
}
</script>

// main.js

import Vue from 'vue'
import router from './components/router.js'

import App from './App'

new Vue({
  router,
  // el: '#app',
  render: h => h(App)
}).$mount('#app')

// index.html

<div id="app">
</div>

[Leonard1980]

I experience the same problem. By the look of Lahori-Jawan’s code, It might be the same as what I experince. Here is the code:

https://github.com/Leonard1980/VueRouterTest

I don’t know what is all about, but I’m guessing it might be a bug on not triggering the hashchange event.

@LinusBorg I posted this also on the forum. Thanks.

[LinusBorg]

…and if it’s not reproducible on jsfiddle (please show!), then create a repository on github.

We work on this in your free-time, and setting up actual reproductions from some code snippets in an issue takes away a lot of our time, while you already possess the exact setup that leads to the problem.