Let’s look at this line of code first:
<script src = "allMyClientSideCode.js"></script>
This is a little... not great. "Where should I put this?" developers will wonder, "Higher up, in the
tag? Or lower down, in the tag?" Either approach will make rich scripts The end of the site was tragic. A large script in the tag will stall all page rendering work, leaving the user in a "white screen of death" state until the script is loaded. The large script at the end of the tag will only let the user see a lifeless static page, and the place where client-side rendering should be performed is scattered with non-functional controls and empty boxes.A perfect solution to this problem requires dividing and conquering scripts: those scripts responsible for making the page look better and easier to use should be loaded immediately, while those scripts that can be loaded later should be loaded later. But how can we decompress these scripts while ensuring their availability when called?
1. Re-understanding the
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
