and static assets

Same point:
  assets and static two static resource files are stored. Project resources needed file images, fonts, icons, style file so you can put these two files.
Not the same point:
  assets stored in static resource files in the project package, which is run npm run time will place the assets in the build static resource files upload package, the so-called packaging simple point can be understood as the volume compression, code formatting. The static resource files compressed ultimately will be placed in the static index.html file along with uploaded to the server; static resource files placed in static compression format would not go packing and other processes, but directly into the packaged good catalog, direct upload to the server. Because the compression avoids direct upload, when packaging will increase the efficiency of some, but static resource files in the absence of compression and other operations, so the file size relative to the file after it's packaged assets to submit a larger point. The server will occupy more space.
 
 
 

Guess you like

Origin www.cnblogs.com/yscec/p/11592730.html