Radovan Lozej

still doesn't solve the issue for me. Vite proxy settings are still overridden by the plugin on the initial load of the page. Lets say I want to open api...

Actually this happens in location-bar lib on https://github.com/KidkArolis/location-bar/blob/master/location-bar.js#L198 on start replaces /#something with /something

ok I solved it by settings location to BrowserLocation with custom options. Setting hashChange: false do the trick ``` const router = Cherrytree({ interceptLinks: true, pushState:true, location: new Cherrytree.BrowserLocation({pushState: true,...

ahh.. that only works for initial router call, further transitions don't work anymore :/

I just want to use pushState (without legacy hash change) where urls may also include hashes. An hash as part of router params and option to enable or disable fallback,...

With hashes included what would then happen when you'll navigate to same path and only the hash part will change? Transition won't fire, right? ..just hash part will change in...

I wouldn't fire transition if only the hash part changes, but url should be updated anyway. It looks like hash change won't fire a page jump (http://lea.verou.me/2011/05/change-url-hash-without-page-jump/) when changed via...

same here. Tried version 0.6.2, above error is gone, but I get a parse error on other JSON files (not locales). `Module parse failed: Unexpected token (2:18) You may need...

when is this fix coming in to release?

It could be created automatically if do not exists yet (initial deploy).