Deno•2y ago

The deployment failed: Relative import path "$fresh/server.ts" not prefixed with / or ./ or ../

When deploying I get this error:

Deploying... (100.0%)
Error: The deployment failed: Relative import path "$fresh/server.ts" not prefixed with / or ./ or ../

Deploying... (100.0%)
Error: The deployment failed: Relative import path "$fresh/server.ts" not prefixed with / or ./ or ../

A person who had the same error on their machine solves this by adding this to the import map:

  "deno.importMap": "./import_map.json"

  "deno.importMap": "./import_map.json"

This doesn't work on my case. In my understanding this shouldn't be an issue at all. Do you know why is that?

Background

My fresh project is under some sub-folder from the root. The structure is like this:

.
├── .github
├── .git
└── deno.json/
    └── 1/
        └── Web/
            ├── main.ts
            └── dev.ts

.
├── .github
├── .git
└── deno.json/
    └── 1/
        └── Web/
            ├── main.ts
            └── dev.ts

deno.json

deno.json

{
  "lock": false,
  "tasks": {
    "check": "deno fmt --check && deno lint && deno check **/*.ts && deno check **/*.tsx",
    "cli": "echo \"import '\\$fresh/src/dev/cli.ts'\" | deno run --unstable -A -",
    "manifest": "deno task cli manifest $(pwd)",
    "start": "deno run -A --watch=static/,routes/ './1/Web/dev.ts'",
    "build": "deno run -A './1/Web/dev.ts' build",
    "preview": "deno run -A ./1/Web/main.ts",
    "update": "deno run -A -r https://fresh.deno.dev/update ."
  },
...
  "exclude": [
    "**/_fresh/*"
  ],
  "imports": {
    "$fresh/": "https://deno.land/x/fresh@1.6.1/",
    "preact": "https://esm.sh/preact@10.19.2",
    "preact/": "https://esm.sh/preact@10.19.2/",
    "@preact/signals": "https://esm.sh/*@preact/signals@1.2.1",
    "@preact/signals-core": "https://esm.sh/*@preact/signals-core@1.5.0",
    "tailwindcss": "npm:tailwindcss@3.3.5",
    "tailwindcss/": "npm:/tailwindcss@3.3.5/",
    "tailwindcss/plugin": "npm:/tailwindcss@3.3.5/plugin.js",
    "$std/": "https://deno.land/std@0.208.0/",
    "daisyui": "npm:daisyui@4.4.19"
  },
...

{
  "lock": false,
  "tasks": {
    "check": "deno fmt --check && deno lint && deno check **/*.ts && deno check **/*.tsx",
    "cli": "echo \"import '\\$fresh/src/dev/cli.ts'\" | deno run --unstable -A -",
    "manifest": "deno task cli manifest $(pwd)",
    "start": "deno run -A --watch=static/,routes/ './1/Web/dev.ts'",
    "build": "deno run -A './1/Web/dev.ts' build",
    "preview": "deno run -A ./1/Web/main.ts",
    "update": "deno run -A -r https://fresh.deno.dev/update ."
  },
...
  "exclude": [
    "**/_fresh/*"
  ],
  "imports": {
    "$fresh/": "https://deno.land/x/fresh@1.6.1/",
    "preact": "https://esm.sh/preact@10.19.2",
    "preact/": "https://esm.sh/preact@10.19.2/",
    "@preact/signals": "https://esm.sh/*@preact/signals@1.2.1",
    "@preact/signals-core": "https://esm.sh/*@preact/signals-core@1.5.0",
    "tailwindcss": "npm:tailwindcss@3.3.5",
    "tailwindcss/": "npm:/tailwindcss@3.3.5/",
    "tailwindcss/plugin": "npm:/tailwindcss@3.3.5/plugin.js",
    "$std/": "https://deno.land/std@0.208.0/",
    "daisyui": "npm:daisyui@4.4.19"
  },
...

Stack Overflow

Deno - Relative import path "$fresh/dev.ts" not prefixed

I have this TypeScript complaint in my editor for a Deno module.

Relative import path "$fresh/dev.ts" not prefixed with / or ./ or ../

There is an import_map.json with this content.
{
...

OokerOP•1/16/24, 6:16 AM

Deno AI Helper•1/16/24, 7:17 AM

Based on the error message you're encountering, it seems that the import map is not being correctly resolved during the deployment process. The error indicates that the import path for is not being recognized as a valid module specifier.

The import map in your

deno.json

deno.json

file appears to be correctly mapping the specifier to the URL. However, the deployment process might not be picking up this import map, or there could be an issue with how the import map is being used in the context of the deployment.

Here are a few steps you can take to troubleshoot this issue:

Ensure the import map is being used: Make sure that the import map is correctly referenced in your
```
deno.json
```
```
deno.json
```
file and that the deployment process is aware of it. If you're using Deno Deploy, the import map should be automatically picked up from the
```
deno.json
```
```
deno.json
```
file.
Check the import map's scope: Verify that the import map's scope includes the files that are using the specifier. Import maps can be scoped to certain directories, and if the scope is not set correctly, it might not apply to all necessary files.
Verify the file structure: Ensure that the file structure of your project matches the paths specified in the import map and the
```
deno.json
```
```
deno.json
```
tasks. The error message suggests that there might be a mismatch between the expected file structure and the actual one.
Check for typos or errors: Double-check the import map and
```
deno.json
```
```
deno.json
```
file for any typos or errors that might be causing the import map to not be recognized correctly.
Test locally: Try running your project locally with the import map to see if the issue is specific to the deployment environment. If it works locally, the problem might

Deno AI Helper•1/16/24, 7:17 AM

be with the deployment setup.

Consult the documentation: The documentation on import maps might provide additional insights or steps to follow to ensure that your import map is being used correctly during deployment.

If you've gone through these steps and the issue persists, it might be helpful to look for similar issues in the Deno community forums or GitHub issues to see if others have encountered and resolved similar problems. Additionally, you can consider reaching out to the Deno community for further assistance.

Helpful Links:
Import Maps | Deno Docs
Using Visual Studio Code | Deno Docs
Changing the source directory | Fresh docs
Deno 1.20 Release Notes

OokerOP•1/26/24, 5:31 AM

anyone?

OokerOP•1/27/24, 8:06 AM

if the path contains a space or a non-ASCII character then it yields this error:

I haven't figured out how to escape those characters.

OokerOP•1/27/24, 12:36 PM

https://github.com/denoland/deploy_feedback/issues/590

GitHub

Error: The deployment failed: Relative import path "$fresh/server.t...

Discussed in denoland/fresh#2246 Originally posted by ooker777 January 13, 2024 When deploying I get this error: Deploying... (100.0%) Error: The deployment failed: Relative import path "$fres...

The deployment failed: Relative import path "$fresh/server.ts" not prefixed with / or ./ or ../

Background

deno.jsondeno.json

`deno.json`
`deno.json`