Replies: 1 comment
-
IIRC Deno didn't want to add a deno specifier for 3rd party modules because it breaks the purpose of url imports. Personally I prefer URL imports and dep.ts/managing import maps. There are 3rd party tools that can do this for you if you want to manage dependencies with a tool. Personally I find it quicker to use deps.ts + url import + intellisense |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Reference: https://github.com/denoland/experimental-deno-specifiers-example/blob/main/02-deno-canonical-app/
project1/import_map.json
:project1/export.ts
:project2/import.ts
:The purpose is to serve as an alternative to
deps.ts
.Beta Was this translation helpful? Give feedback.
All reactions