How does the webpackJsonp is not defined report an error when the vue.js project is packaged into a formal environment?
after the vue project is packaged and released to the production environment, the refresh page will sometimes find that the page cannot be loaded, and then f12 will view it and return the following error:
vendor.xxx.jsmanifest.xxx.jswebpackjsonpvendor.xxx.jsmanifest.xxx.js
Note: the figure above shows the details of the request with an error webpackJsonp is not defined ( menifest.xxx.js file appears twice)
but a strange problem is that the manifest.xxx.js file in the figure above appears twice, but the first file does not have a webpackjsonp function. If there is no webpackJsonp is not defined error, manifest.xxx.js will only appear once in the corresponding request list!
The
problem is found, mainly because vendor.xxx.js takes precedence over manifest.xxx.js loading. How to deal with this problem?
Note: Local development environment and test environment it is difficult to reproduce this problem, is there any way?
this is the server that sets the cache to enter for the first time should be no problem.
change the generation order of CommonsChunkPlugin in webpack.config.js. Try
.
has also encountered this problem, and there is no solution.
this problem occurs occasionally, sometimes it doesn't come out once in half a day, and sometimes it happens three or four times out of 10 refreshes
when you look up materials on the Internet, you always say that the public file manifest.xxx.js must first vendor.xxx.js be loaded. After I read the packaged index.html file, manifest.xxx.js was indeed introduced before vendor.xxx.js .
the js file introduced by < / script > is loaded from top to bottom, but I don't know why the situation in your screenshot appears. vendor.xxx.js first manifest.xxx.js is loaded. It seems to be loaded asynchronously.
perhaps familiar with vue-cli and webpack related configuration, can find the setting item about asynchronous loading
this is a cross-domain problem. The server sets a reverse proxy!
https://codeshelper.com/a/11.
is a similar problem, but my manifest.xxx.js does not read the manifest.xxx.js, generated in npm run build, so the display error causes webpackJsonp is not defined,. Does anyone have a solution
I have the same problem as the landlord
is there any solution
I would like to ask whether this problem has been solved. Can you talk about the solution
the same as above, the buddy who has solved the solution posted the solution
Big Brother, have you solved this problem? I also have the same problem. If it is solved, is it possible to bask in the sun?
all tm deceives people. Enter the packaged vender file to determine whether webpackJsonp exists, and there is no forced refresh page. Simply and rudely
first check whether some file 404 errors are reported? Is the formal environment deployed on different servers? The server accesses files with different IP addresses during load balancing, so the project needs to be packaged locally. Make sure that the filenames built in projects deployed in formal environments with different IP addresses are the same, so that there will be no inaccessible problems
