You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It works well if served from a http-serve or web server or whatever - but if the dist file is opened as a file:///...path...to../index.html directly in the browser, the route automatically changes to file:///#/ losing the whole file path and name.
The text was updated successfully, but these errors were encountered:
This is indeed a problem. The current usage of hash history assumes a web server and uses the History API with a base of /# but that won't work on file:///. I will have to investigate that more but for the moment using a Web History with a base of # makes it work:
I have the following router...
It works well if served from a http-serve or web server or whatever - but if the dist file is opened as a
file:///...path...to../index.html
directly in the browser, the route automatically changes tofile:///#/
losing the whole file path and name.The text was updated successfully, but these errors were encountered: