.sst/.sst/ directory within my project. The .sst/.sst/ directory contains SST’s internal tooling, including its own package.jsonpackage.json and node_modulesnode_modules..sst/.sst/ targetting the npm ecosystem, but Deno treats .sst/.sst/ like any other source code in the project, e.g., expects import foo from 'npm:bar'import foo from 'npm:bar' instead of … from ‘bar’… from ‘bar’, or import { add } from ‘./calc.ts’import { add } from ‘./calc.ts’ instead of … from ‘./calc’… from ‘./calc’.patchpatch field in deno.jsondeno.json . Per the docs, patchpatch is currently limited to JSR packages."unstable": ["sloppy-imports"]"unstable": ["sloppy-imports"] to deno.jsondeno.json. But, deno checkdeno check fails with errors like:.sst/.sst/ as an npm module.Join the Discord to ask follow-up questions and connect with the community