npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@azure/bicep-deploy-common

v0.6.7

Published

Common Code for bicep-deploy (GitHub Action/ADO Task)

Readme

Bicep Deploy Common

This package contains code that is commonly used between the bicep-deploy GitHub Action and Azure Pipelines Task.

Usage

Importing

Install this package and reference:

import { Logger } from "@azure/bicep-deploy-common";

Logging external output

Logger keeps task-owned messages separate from values that can be influenced by Azure responses, repository content, or child processes. Implementations must route logExternalOutput through the host runner's command-safe output mechanism and preserve both the source and level:

logger.logExternalOutput(message, {
  source: "remote",
  level: "warning",
});

The common package classifies output but does not apply runner-specific escaping. Azure Pipelines and GitHub Actions adapters are responsible for preventing external text from being interpreted as runner commands.

Azure SDK debug logging emits request and response metadata such as the method, URL, status, correlation ID, and activity ID. It intentionally omits request and response bodies because deployment payloads can contain parameters, outputs, nested errors, and other sensitive values.

ARM error handling

Deployment and deployment stack clients preserve structured ARM error responses, including nested error details and correlation IDs, through a shared pipeline policy. This applies to initial requests and long-running operation polling, without changing the SDK's retry behavior or the initial deployment poll delay. Responses without a structured ARM error remain subject to normal SDK handling.

Validating the packed package

Run npm run test:consumer to build and pack the package, install the tarball into a clean temporary fixture, and validate:

  • published files and declaration entry points;
  • root, deployments, and stacks imports at compile time and runtime; and
  • the public subpath mocking behavior used by the Azure Pipelines task tests.

The command removes the generated tarball and temporary fixture after it finishes.

The package-upload workflow uses npm run pack:validate after stamping and building both shared packages. That command retains and reports the exact validated tarballs so the workflow uploads the same files rather than repacking after validation. The common tarball is stamped with an exact dependency on the validated RPC tarball, while the workspace manifest is restored to its development-time wildcard dependency after packing. Fixture installation uses strict npm engine enforcement.

Running unit tests

From this package directory, run npm test for Vitest watch mode or npm test -- --run for a single run.

From the repository root, use the workspace command:

npm test --workspace @azure/bicep-deploy-common -- --run