Deno•2y ago

How to define local import maps?

I got these things in the tests above:

import { assertAlmostEquals, assertEquals } from "@std/assert";
import { Vector2 } from "../src/math/mod.ts";
import { QUARTER_PI } from "../src/utils/math.util.ts";

import { assertAlmostEquals, assertEquals } from "@std/assert";
import { Vector2 } from "../src/math/mod.ts";
import { QUARTER_PI } from "../src/utils/math.util.ts";

Notice how I have to do a lot of

./

./

js to get to the next? I understand there'st the

"imports": {}"

"imports": {}"

support in

deno.json(c)

deno.json(c)

, and I do remember using smth like Bun's

package.json

package.json

"workspace": []

"workspace": []

system to create localised

@one/two

@one/two

, complete with

index.ts

index.ts

in their respective folders for exports.

Are there are examples on defining local import maps?

Deno AI Helper•6/26/24, 10:05 PM

To define local import maps in Deno, you can use the field in your

deno.json

deno.json

deno.jsonc

deno.jsonc

configuration file. Import maps allow you to create aliases for your module paths, which can simplify imports in your project and avoid the repetitive use of relative paths like

./

./

and

../

../

.

Here's a step-by-step guide on how to define local import maps based on the documentation:

Create a
```
deno.json
```
```
deno.json
```
or
```
deno.jsonc
```
```
deno.jsonc
```
file in the root of your project if you don't already have one.
Inside the configuration file, add an `importMap` field with the path to your import map file. For example:```json{ "importMap": "./import_map.json"}```
Create an file (or whatever you named it in the previous step) in your project.
Define your import map by specifying the aliases and the corresponding paths. For example:```json{ "imports": { "@std/": "https://deno.land/std/", "@utils/": "./src/utils/", "@math/": "./src/math/" }}```
Now, you can use these aliases in your imports. For instance:```tsimport { assertAlmostEquals, assertEquals } from "@std/assert";import { Vector2 } from "@math/mod.ts";import { QUARTER_PI } from "@utils/math.util.ts";```
When running your Deno commands, make sure to include the `--importmap` flag followed by the path to your import map file. For example:```shdeno run --importmap=import_map.json your_script.ts```

The documentation also mentions that the

deno.json

deno.json

file is auto-discovered and acts, among other things, as an import map. This means that once you have your

deno.json

deno.json

and import map file set up, Deno will automatically use the import map when resolving module imports.

Remember that the import map file

Deno AI Helper•6/26/24, 10:05 PM

must be a valid JSON file and follow the import map specification.

If you need more specific examples or further clarification, the documentation provides detailed information on how to use import maps in Deno.

Helpful Links:
ECMAScript Modules in Deno | Deno Docs
Importing & Exporting - Deno by Example
Deno Runtime Quick Start | Deno Docs
Importing JSON - Deno by Example
Why We Added package.json Support to Deno
deno.json configuration file
Import Maps

KawaxteOP•6/27/24, 6:03 AM

it worked by js putting my own things in

Doctor 🤖•6/27/24, 6:14 AM

Idk why it said to make an external import map file when using

imports

imports

in deno.json works just fine.

DDoctor 🤖Idk why it said to make an external import map file when using `imports` in deno...

KawaxteOP•6/27/24, 11:07 AM

Yeah, I know about the standard new one

KawaxteOP•6/27/24, 11:07 AM

I did js that

KawaxteOP•6/27/24, 11:08 AM

I didn't think you could js do it like that

KawaxteOP•6/27/24, 11:08 AM

Would be nice to be able to define esbuild as an import map though...

KawaxteOP•6/27/24, 11:08 AM

Has errors if I do, so I have to use

Doctor 🤖•6/27/24, 11:08 AM

Doctor 🤖•6/27/24, 11:09 AM

I have no problems including esbuild in the imports.

DDoctor 🤖I have no problems including esbuild in the imports.

KawaxteOP•6/27/24, 11:09 AM

Which url variant?

Doctor 🤖•6/27/24, 11:10 AM

KawaxteOP•6/27/24, 11:10 AM

esh variant complains about "declare as export"

DDoctor 🤖```json "esbuild": "npm:esbuild" ```

KawaxteOP•6/27/24, 11:10 AM

Ach, but that creates a

node_modules

node_modules

, no?

Doctor 🤖•6/27/24, 11:10 AM

You don't see one in the project.

KawaxteOP•6/27/24, 11:10 AM

so it'st hidden?

Doctor 🤖•6/27/24, 11:10 AM

I'm pretty sure it's creating one in the same place its caching other stuff

KawaxteOP•6/27/24, 11:11 AM

ach so

KawaxteOP•6/27/24, 11:11 AM

was rly hoping to be able to use denoland's variant directly as an import map

KawaxteOP•6/27/24, 11:11 AM

Which I'm currently using in deps

Doctor 🤖•6/27/24, 11:15 AM

I've more or less abandoned denoland since JSR came out

Doctor 🤖•6/27/24, 11:15 AM

But not everything is on JSR so I just resort to npm if it's not.

KawaxteOP•6/27/24, 11:16 AM

Where do you check for jsrs?

Doctor 🤖•6/27/24, 11:17 AM

Have you not heard of JSR?

Doctor 🤖•6/27/24, 11:17 AM

https://jsr.io/

JSR: the JavaScript Registry

JSR is the open-source package registry for modern JavaScript. JSR natively supports TypeScript, and works with all JS runtimes and package managers.

KawaxteOP•6/27/24, 11:17 AM

nnnnope

KawaxteOP•6/27/24, 11:17 AM

I'm relatively new to the -script system

Doctor 🤖•6/27/24, 11:17 AM

Deno moved to it a while ago now

KawaxteOP•6/27/24, 11:18 AM

I see

KawaxteOP•6/27/24, 11:19 AM

I initially came from Bun

Doctor 🤖•6/27/24, 11:19 AM

They came out with JSR to solve a few problems that existed with NPM and https imports

Doctor 🤖•6/27/24, 11:21 AM

The problem with NPM is that it hasn't been updated in ages to handle the modern way we write and consume code these days, often making you jump through hoops to not only publish code there, but also consume code. The problem with https imports is deduplication. When different libraries depend on different but similar versions of the same dependency, with https imports you'd have duplicate code, but with JSR they can serve you one version that is compatible with both.

DDoctor 🤖The problem with NPM is that it hasn't been updated in ages to handle the modern...

KawaxteOP•6/27/24, 11:22 AM

I don't know anything about that but I trust you in this, so I'll js move what I have to jsr when I can.