Skip to content
This repository was archived by the owner on Mar 11, 2021. It is now read-only.

Extension fails with different DENO_INSTALL #17

Open
phil294 opened this issue Jan 26, 2020 · 0 comments
Open

Extension fails with different DENO_INSTALL #17

phil294 opened this issue Jan 26, 2020 · 0 comments

Comments

@phil294
Copy link

phil294 commented Jan 26, 2020

I installed Deno, as mentioned in the docs, with curl -fsSL https://deno.land/x/install/install.sh | sudo DENO_INSTALL=/usr/local sh. As such, the folder ~/.deno doesnt exist.

Steps necessary for a working deno environment were:

  1. Create ~/.deno manually
  2. deno types > ~/.deno/deno.d.ts
  3. Adjust the http/s paths in tsconfig.json to /home/[user]/.cache/deno/deps/... as this is where deno caches the dependencies by default, I think..? Maybe this should be dynamically detected using deno info?
  4. Add import 'deno'; to the top of the source file, as Deno cannot be found otherwise
  5. Optional: Remove node_modules, package.json and package-lock.json.

Not really sure why the deno vscode npm plugin is necessary or what it does, but the TS support works just as fine without. In fact, I removed the entire extension again after all above steps since it was not required anymore obviously. Thanks for all the work anyway. Hopefully this will help in getting things aligned again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant