Based on the documentation, Deno does not have a concept of "peer dependencies" like in Node's npm. In Deno, modules are imported directly via URLs and there is no package manager.
However, Deno does provide a way to manage dependencies through a deps.ts file. This file is used to import and re-export your dependencies. This way, you can manage all your dependencies in one place and avoid having multiple references to the same URL throughout your project.
If you have a dependency that is used in several files, upgrading to a new version of this dependency is much simpler as this can be done just within deps.ts.
In your case, you could import both Pentagon and Zod in your deps.ts file and re-export them for use in your project. However, if Pentagon and your project require different versions of Zod, this could lead to conflicts.
The documentation also mentions the Duplicate Dependency Problem, which arises when a program contains similar yet slightly different modules. If another module imports a URL referencing a slightly different version, both module versions will be included in the module graph despite being almost the same code.
Unfortunately, the documentation does not provide a clear solution to this problem. It does mention the use of import maps as a potential solution, but notes that import maps are not composable and cannot be used by a published library and an import map simultaneously.
Therefore, based on the information provided in the documentation, it seems that there is no straightforward way to mark a dependency as "peer" in Deno.
vale sparrow
turbid sequoia
strange frost