React routing webpack debugging is normal, but the packaged routing does not work.

the server port 8080 of webpack is well developed and debugged. The local port 80 can only open the home page, and all other paths are
[an error occurred while processing this directive] The requested URL was not found on this server.. If you entered the URL manually please check your spelling and try again. [an error occurred while processing this directive]
this is the page error message
below is the console error message
Error in event handler for (unknown): TypeError: Cannot read property "textContent" of null
at displayError (chrome-extension://chklaanhfefbnpoihckbnefhakgolnmc/content.js:4:99)
at chrome-extension://chklaanhfefbnpoihckbnefhakgolnmc/content.js:282:4

Node.js javascript html react.js

Mar.21,2021

if you only look at the error message in the console, the textContent field should be used on the page. However, if the value of this field is null, you can check whether the textContent field in the API response parameters has a value, or check where textContent is used on the page, and make a non-empty judgment

Previous: Why does python modify the global int variable in the method of the class without reporting an error but invalid after adding global?

Next: Python uses filter to find primes