The latest articles on DEV Community by Frederick (@frederick). https://dev.to/frederick https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F652108%2F06a4248e-9088-46ec-9f85-da916b7a8c83.png https://dev.to/frederick en Frederick Sat, 19 Jun 2021 12:38:54 +0000 https://dev.to/frederick/npm-multi-version-package-4p39 https://dev.to/frederick/npm-multi-version-package-4p39 <p>Hi,</p> <p>My and my team are implementing a multi build process in our deploy CI/CD flow.</p> <p>By configuring babel/webpack properly we are now able to ship different versions of our codebase per browser.</p> <p>However from what I saw, when it come to the packages used by the application in node_modules, they do not all the time offer modern/legacy etc versions through "Exports/mains" package.json fields</p> <p>I wonder if is there any best practices standard for package publisher is this regard. and if is possible to know easily which packages offer many version.</p> <p>Thank! </p> npm help