How do front-end projects managed by npm+webpack handle public third-party libraries for use by other subprojects?

A large project is split into several independently developed small projects, and there is bound to be a common third-party library between small projects. According to the normal independent development process, it is certain that each small project depends on the third-party library it needs, but this will lead to multiple third-party library files in the final large project. I would like to ask how do the bosses who really encounter such a situation deal with it? Is it that there are multiple third-party library files in large projects? Or can you manage a shared third-party library in some way and take care that there is only one shared third-party library file for the last big project?


webpack packaging optimization, you can take a look in this direction.
one of the keywords: DLL


not only there are multiple third-party libraries in different projects, but sometimes it is difficult to ensure that the versions of the third-party libraries in each project are the same. If we submit the first-party library to npm ourselves, we may urge you to use the latest version.

MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-1b380f9-2b85e.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-1b380f9-2b85e.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?