Skip to content

VSCode extension compatibility  #638

@dangdennis

Description

@dangdennis

Re: forum thread

I demonstrated that deno can the rescript&friends binary from npm and build locally. But the vscode extension doesn't work because deno caches the files in a deno-specific directory. However, if you run deno run --node-modules-dir entrypointfile.ts, we get a node_modules folder for the extension.

However, I'd like to make it even easier to use without the --node-modules-dir option.

It looks like constants.ts evaluates a path to the binary depending on env.

On arm64 m1 apple, deno info returns our cache locations

DENO_DIR location: /Users/dennisdang/Library/Caches/deno
Remote modules cache: /Users/dennisdang/Library/Caches/deno/deps
npm modules cache: /Users/dennisdang/Library/Caches/deno/npm
Emitted modules cache: /Users/dennisdang/Library/Caches/deno/gen
Language server registries cache: /Users/dennisdang/Library/Caches/deno/registries
Origin storage: /Users/dennisdang/Library/Caches/deno/location_data

The rescript binary lives within ~/Library/Caches/deno/npm/registry.npmjs.org/rescript/.

Despite the available workaround, is there any interesting in supporting a Deno "natively"?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions