1. When the first get route is parsed successfully, the server will render content1 directly without waiting for the second one. This is why there is a next in the parameter.
2. In express, the order of routes is next to each other. If you do not use next, then only the callback method in the first get() will be triggered by default.
Solution
Synchronize query and finally render together
I am also a novice, I wrote some code for you to explain the logic problem
Why
1. When the first get route is parsed successfully, the server will render content1 directly without waiting for the second one. This is why there is a next in the parameter.
2. In express, the order of routes is next to each other. If you do not use next, then only the callback method in the first get() will be triggered by default.
Solution
Synchronize query and finally render together
I am also a novice, I wrote some code for you to explain the logic problem