After the vue project is packaged (dist folder), the access effect of the page under the local nginx is different from that under the Linux server nginx. What is the problem?

1, local project uses WebStrom for development, vue framework;
2, when the project runs (npm run dev), in development mode, each function performs as expected, mainstream browsers (chrome, firefox, QQ, 360, Sogou) have good compatibility;
3, packaged (npm run build) generates a dist folder under the project root directory;
4, put the dist folder under the html folder under the local nginx, add the virtual server node information to the configuration file of nginx, and access it on the local machine. The access effect of various major browsers (chrome, firefox, QQ, 360, Sogou) is the same as that of the project running (npm run dev) in development mode.
5, compress the dist folder (7-Zip is packaged into a .tar file), upload it to the Linux server through rz-be, put it under the html of nginx, decompress it with tar-xvf, and the server nginx configuration information and version on Linux are the same as the local nginx information. When you visit the page on the Linux server, chrome, firefox and Sogou browsers perform normally, which is no different from the local development mode; IE, QQ,360 browsers display different results on font, scroll bar and textarea placeholder, and textarea still stutters when entering.
what may be the reason and how to investigate?

Linux css html nginx
Oct.15,2021

from your problem description, it is not confirmed that the IE browser access development mode is normal? Please make sure that if the IE browser accesses the development mode or the local nginx is not normal, this is the most common IE compatibility problem, which requires your code to do special treatment for the IE browser. If the IE browser accesses the development mode or the local nginx is normal, but the server nginx is not normal, it is strange. You can compare the difference between the html obtained from the server nginx and the html obtained by the local nginx. According to the different analysis, generally speaking, it is unlikely that the html is the same, but one is normal and the other is abnormal.

  1. for browsers that display exceptions, do you open the console to see if error or warning is generated.
  2. chrome and firefox display normally, and I understand that there should be no problem getting page content from linux, because both browsers support the web standard very well.
  3. if there is a problem on linux due to local windows, see if the text wrapping or encoding is different between different systems, and some browsers do not handle this situation well.

have you solved the same problem?

Previous: A regular expression that matches the part between An and B. if there is no B, take the part after A.

Next: Flask blueprint how do multiple routes use the same before_request method?

css mysql arrays josn react html typescript webpack npm sass R objective-c .net sql-server jquery python-3.x angularjs django angular excel regex iphone ajax linux xml pandas vba spring database wordpress string wpf xcode windows bash postgresql oracle multithreading eclipse list firebase algorithm macos forms image scala visual-studio azure bootstrap spring-boot react-native python-2.7 docker performance function winforms matlab powershell apache dataframe api sqlite numpy rest shell selenium flutter dart maven loops qt swing android-studio csv express file class tensorflow sorting codeigniter perl
© 2021 CodesHelper
Advertising Contact us About us
Menu