Magnus

I have the same problem. Using Azure CLI. Checked with the Dashboard, no app exists with the name I am using.

**EDIT:** I added a minimal repo and steps to reproduce, to the OP.

Thanks for chiming in @valentinpalkovic . I decided to set up tooling to prevent different versions of packages across the monorepo. A bit clumsy, but works well now that it...

If I create replicas of a container, and use a port range, I still get that same error message: **Compose file excerpt:** ```yml ports: - target: 3000 published: "3000-3010" mode:...

> If I create replicas of a container, and use a port range, I still get that same error message: > > **Compose file excerpt:** > > ```yaml > ports:...

In case helpful to others, I am now using Syncpack to keep packages in monorepos on the same version. It works well, but it would be nice if the package...

@mcollina I noticed that `ThreadStream` (the return type of `transport(..)`) is `any`. Is there a reason we do not just set it to be `DestinationStream`? That would match with what...

@carsonb I ended up getting an issue runtime, when `pino` was in the `config.externals` list. In short, it did not exist in runtime ( which is probably not that surprising,...

> > Sorry about the somewhat off topic comment but I fail to understand what benefit using this would bring to a Next.js app? We're currently using Pino 7 with...

> Sorry about the somewhat off topic comment but I fail to understand what benefit using this would bring to a Next.js app? We're currently using Pino 7 with Next.js...