https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/libraries/javascript/Recent content in Chainguard Libraries for JavaScript onHugo -- gohugo.ioen-USThu, 05 Jun 2025 09:00:00 +0000https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/libraries/javascript/overview/Thu, 05 Jun 2025 09:00:00 +0000https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/libraries/javascript/overview/Chainguard Libraries for JavaScript is a major ecosystem supported by Chainguard Libraries. The JavaScript ecosystem consists of thousands of open source projects from the communities around JavaScript, TypeScript, Node.js, React, Vue.js, Angular, Svelte, Next.js, Express, and many others. Background The main public repository for JavaScript packages is the npm Registry. Launched in 2010, the npm Registry has grown to become the largest software registry in the world, hosting over two million packages.https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/libraries/javascript/global-configuration/Thu, 05 Jun 2025 09:00:00 +0000https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/libraries/javascript/global-configuration/JavaScript and npm package consumption in a large organization is typically managed by a repository manager. Commonly used repository manager applications are JFrog Artifactory, Sonatype Nexus Repository, and others. The repository manager acts as a single point of access for developers and development tools to retrieve the required libraries. At a high level, adopting the use of Chainguard Libraries consists of the following steps: Add the Chainguard Libraries for JavaScript registry as a remote repository for library retrieval.https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/libraries/javascript/build-configuration/Thu, 05 Jun 2025 09:00:00 +0000https://deploy-preview-3050--ornate-narwhal-088216.netlify.app/chainguard/libraries/javascript/build-configuration/The configuration for the use of Chainguard Libraries depends on your build tools, continuous integration, and continuous deployment setups. At a high level adopting the use of Chainguard Libraries consists of the following steps: Remove local caches on workstations and CI/CD pipelines. This step ensures that any libraries that were already sourced from other repositories are requested again and the version from Chainguard Libraries is used instead of other binaries. Change configuration to access Chainguard Libraries via your repository manager after the changes from the global configuration are implemented.