This repository was archived by the owner on Mar 11, 2021. It is now read-only.
This repository was archived by the owner on Mar 11, 2021. It is now read-only.
Extension fails with different DENO_INSTALL #17
Open
Description
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:
- Create
~/.deno
manually deno types > ~/.deno/deno.d.ts
- 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 usingdeno info
? - Add
import 'deno';
to the top of the source file, asDeno
cannot be found otherwise - Optional: Remove
node_modules
,package.json
andpackage-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.
Metadata
Metadata
Assignees
Labels
No labels