i'm guessing tooling hasn't quite gotten up to speed with deno yet, so here's something to smooth things over
when deno says tsconfig.json is not needed..... it also means intellisense for the Deno global namespace won't be inferred, leading to red squiggly marks on your nice deno file whenever you use Deno.<something>
as a result, if you want deno to have all the niceties of typescript, you need:
deno types)below is a gist for setting it up (which requires package.json. the irony is not lost on me.)
{
"name": "deno-with-setup",
"version": "1.0.0",
"description": "",
"main": "app.ts",
"scripts": {
"start": "deno run app.ts",
"setup": "npm run setup:tsconfig && npm run setup:deno",
"setup:tsconfig": "echo {\"compilerOptions\": { \"types\": [\"./deno.d.ts\"] }} > tsconfig.json",
"setup:deno": "deno types > deno.d.ts"
},
"keywords": [],
"author": "panzerstadt",
"license": "ISC"
}