base44 0.1.33 installation blocked by pnpm blockExoticSubdeps (@deno/loader URL dependency) #670

Environment

• Windows
• Node.js 24.19.0 (satisfies the package's >=20.19.0 requirement)
• pnpm 11.25.0
• base44 0.1.33
• blockExoticSubdeps enabled

Observed failure

Running pnpm dlx base44 login stops during dependency resolution, before the CLI starts:

ERR_PNPM_EXOTIC_SUBDEP
Exotic dependency "@deno/loader" (resolved via url) is not allowed in subdependencies when blockExoticSubdeps is enabled
This error happened while installing dependencies of base44@0.1.33

The published manifest declares:

"@deno/loader": "https://npm.jsr.io/~/11/@jsr/deno__loader/0.5.0.tgz"

This appears to be a dependency-source policy conflict, rather than a Node engine mismatch. The security setting has not been disabled, and no alternate installer was used to bypass it.

Could you provide a supported packaging correction or installation route that works with this protection remaining enabled?

Related generic development questions

1. Does base44 exec --data-env dev isolate only records, or is there a supported way to test entity schema/default changes and backend resources without changing production resources?
2. Does updateMany({id, revision}, {$set: {...}, $inc: {revision: 1}}) atomically recheck the predicate at write time, so two competing updates for the same revision produce exactly one successful update? Can callers rely on success, updated and has_more to distinguish one update from zero for this use case?

Documentation references:

• https://pnpm.io/settings/dependency-resolution#blockexoticsubdeps
• https://docs.base44.com/documentation/managing-app-data/testing-your-data
• https://docs.base44.com/developers/references/sdk/docs/type-aliases/entities