


How to deal with the problem that the rendered page is not reflected when Vue routing is refreshed in history mode
This time I will bring you vueroutingHow to handle the problem of rendering the page without reflection when refreshing in history mode, and how to handle the problem of rendering page without reflection when vue route is refreshed in history modeNotes What are the actual cases? Let’s take a look at them.
Solve the problem that vue-router nested routing (sub-routing) cannot render the page when refreshing in history mode. The specific content is as follows
1. Exception description
Originally, the hash mode of vue-router was used, but the URL in hash mode needs to have the "#" symbol, which not only looks uncomfortable, but also destroys the "#" in the routing in some scenarios (the WeChat sharing page will change " #"The following content is processed), so you need to use the history mode, and then let the backend change the nginx configuration:
location / { try_files $uri $uri/ /index.html; }
vue-router uses history mode and uses nested routing:
const router = new Router({ mode: 'history', routes: [ { path: '/', component: mall, name: 'mall' }, …… //我的银行卡 { path: '/myCard', meta: { requireAuth: true }, component: myCard, name: 'myCard', children:[ { path:'', component: card}, { path:'add', component: add} ] } …… ] })
When accessing the routing and nested routing pages, the display is normal, but when refreshing the page, the nested routing page has an exception:
The page style is completely messed up. Take a look at the static files loaded by the page request. All static files are 404;
2. Exception analysis
1. Read the official documentation’s description of nested routing:
2. Looking at the previous exception page again, it seems that our parent route has become the root directory. Check the file path:
3. Take a look at the exception files we introduced. They are referenced directly in the index.html file, that is, they are introduced under the root path. In the previous hash mode, the root path will not change, so it is feasible for us to directly introduce these static files in the index.html file. However, after using the history mode, the root path is not fixed. Then this introduction method is not feasible, which is why the page above cannot be rendered:
3. Solve the problem
It’s a bit awkward here. I first considered introducing static style files in the main Vue by way of Import, which was indeed feasible. However, in the end I found that it was OK to directly modify the static file introduction path in the index.html file:
Before modification:
<script></script>
After modification
<script></script>
4. Principle
./ refers to the current directory where the user is located (relative path);
/ refers to the root directory (absolute path, project root directory), which is the project root directory;
For hash mode, the root path is fixed, which is the root directory of the project. However, in history mode, nested paths starting with /
will be regarded as the root path, so use "./" to introduce files. The file will not be found because the file itself is in the project root directory and is not in the nested path directory.
Summary, regardless of hash mode or history mode, you can directly use "/" to introduce static files from the project root directory.
PS: I encountered this problem some time ago. After searching on Baidu for a long time, I found that few people asked this question, and no one answered it. I also asked many front-end experts, but still couldn't solve this problem. Maybe it’s because I’m used to writing “./” And the path starting with "../", I didn't notice the problem of the way to introduce static files, and tried many methods. Finally, I found out embarrassingly that the problem was actually very simple, it was just that I didn't have a thorough understanding of the underlying framework!
I believe you have mastered the method after reading the case in this article. For more exciting information, please pay attention to other related articles on the php Chinese website!
Recommended reading:
How to connect node.js to MySQL
Detailed explanation of the steps to implement react server rendering
The above is the detailed content of How to deal with the problem that the rendered page is not reflected when Vue routing is refreshed in history mode. For more information, please follow other related articles on the PHP Chinese website!

Python and JavaScript each have their own advantages, and the choice depends on project needs and personal preferences. 1. Python is easy to learn, with concise syntax, suitable for data science and back-end development, but has a slow execution speed. 2. JavaScript is everywhere in front-end development and has strong asynchronous programming capabilities. Node.js makes it suitable for full-stack development, but the syntax may be complex and error-prone.

JavaScriptisnotbuiltonCorC ;it'saninterpretedlanguagethatrunsonenginesoftenwritteninC .1)JavaScriptwasdesignedasalightweight,interpretedlanguageforwebbrowsers.2)EnginesevolvedfromsimpleinterpreterstoJITcompilers,typicallyinC ,improvingperformance.

JavaScript can be used for front-end and back-end development. The front-end enhances the user experience through DOM operations, and the back-end handles server tasks through Node.js. 1. Front-end example: Change the content of the web page text. 2. Backend example: Create a Node.js server.

Choosing Python or JavaScript should be based on career development, learning curve and ecosystem: 1) Career development: Python is suitable for data science and back-end development, while JavaScript is suitable for front-end and full-stack development. 2) Learning curve: Python syntax is concise and suitable for beginners; JavaScript syntax is flexible. 3) Ecosystem: Python has rich scientific computing libraries, and JavaScript has a powerful front-end framework.

The power of the JavaScript framework lies in simplifying development, improving user experience and application performance. When choosing a framework, consider: 1. Project size and complexity, 2. Team experience, 3. Ecosystem and community support.

Introduction I know you may find it strange, what exactly does JavaScript, C and browser have to do? They seem to be unrelated, but in fact, they play a very important role in modern web development. Today we will discuss the close connection between these three. Through this article, you will learn how JavaScript runs in the browser, the role of C in the browser engine, and how they work together to drive rendering and interaction of web pages. We all know the relationship between JavaScript and browser. JavaScript is the core language of front-end development. It runs directly in the browser, making web pages vivid and interesting. Have you ever wondered why JavaScr

Node.js excels at efficient I/O, largely thanks to streams. Streams process data incrementally, avoiding memory overload—ideal for large files, network tasks, and real-time applications. Combining streams with TypeScript's type safety creates a powe

The differences in performance and efficiency between Python and JavaScript are mainly reflected in: 1) As an interpreted language, Python runs slowly but has high development efficiency and is suitable for rapid prototype development; 2) JavaScript is limited to single thread in the browser, but multi-threading and asynchronous I/O can be used to improve performance in Node.js, and both have advantages in actual projects.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Dreamweaver Mac version
Visual web development tools

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

Notepad++7.3.1
Easy-to-use and free code editor

Atom editor mac version download
The most popular open source editor

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment
