Udit Karode
8a926e8cc7
* fix(deno): only collect workspace members when workspaces are declared A package.json with no workspaces field has no members to find, but the member scan ran anyway, and find-packages with no patterns returns every package.json in the tree. Standalone subprojects were picked up as members of the root lock, which is what breaks lockFileMaintenance. The scan now runs only when workspaces are declared. * test(deno): use await expect().resolves Required by the `vitest(prefer-expect-resolves)` oxlint rule enabled on main since this branch was created. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Michael Kriese <michael.kriese@mend.io> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Extracts dependencies from the Deno's projects deno.json and deno.jsonc files.
The deno manager also supports the package.json file for Deno's node-compat as long as a deno.lock file is placed next to the package.json file. It could support another lock filename that specified in deno.json or deno.jsonc.
Supported Dependency Types
The following depTypes of deno.json or deno.jsonc are currently supported by the deno manager:
importsscopes.<mapping>.<specifier>tasks.<name>,tasks.command.<name>: Renovate will not update any lock files.compilerOptions.types,compilerOptions.jsxImportSource,compilerOptions.jsxImportSourceTypeslint.plugins
Additionally, an import map JSON file containing imports and scopes.<mapping>.<specifier> like the examples above is supported.
The deno manager also supports some depTypes that supported by npm manager.
!!! note Deno cli supports private npm compatible registries itself, however the deno managaer is not yet ready to support Private npm module.
!!! note In source dependencies are not supported.
import { assert } from 'jsr:@std/assert@1.0.0';