robin
robin•12h ago

import aliases fail if I move them from tsconfig.json to deno.json (Astro project, VS code)

Hi, I'm trying to migrate an Astro project to Deno. The issue I'm currently facing is that when I move path aliases from tsconfig.json to deno.json everything stops being resolved. For example, I'm trying to delete this file: 
{
  "extends": "astro/tsconfigs/strict",
  "include": [".astro/types.d.ts", "**/*"],
  "exclude": ["dist"],
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@l/*": ["src/layouts/*"]
    }
  }
}
{
  "extends": "astro/tsconfigs/strict",
  "include": [".astro/types.d.ts", "**/*"],
  "exclude": ["dist"],
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@l/*": ["src/layouts/*"]
    }
  }
}
and modify deno.jsonc like so: 
{
  //...
  "imports": {
    /* Local aliases */
    "@l/": "./src/layouts/",
    /* Modules */
    "@astrojs/mdx": "npm:@astrojs/mdx@^4.3.4",
    "astro": "npm:astro@^5.12.9",
    // etc.
  },
  "unstable": ["fmt-component"],
  "nodeModulesDir": "auto"
}
{
  //...
  "imports": {
    /* Local aliases */
    "@l/": "./src/layouts/",
    /* Modules */
    "@astrojs/mdx": "npm:@astrojs/mdx@^4.3.4",
    "astro": "npm:astro@^5.12.9",
    // etc.
  },
  "unstable": ["fmt-component"],
  "nodeModulesDir": "auto"
}
This leads to errors like this: 
-Cannot find module '@l/Base.astro' or its corresponding type declarations. ts(2307)
-Cannot find module '@l/Base.astro' or its corresponding type declarations. ts(2307)
The deno extension is installed and running, and .vscode/settings.json has { "deno.enable": true }. I also tried installing @deno/vite-plugin but I can't get it to work (different issue I believe) so I'm not sure if it would help at all. I'd really like to be able to use deno.json exclusively, I think adding the path aliases there in the imports map make a lot more sense than in some typecript config file. (Why is TS in charge of aliasing my imports? seems really arbitrary to me.) I think maybe the issue is because the files are .astro and not .ts and therefore Deno's LSP is not handling them? But I'm not sure how to fix that. Beyond that, I'd love to know if there are any other steps I'd need to take to be able to fully get rid of tsconfig.json, just to keep a cleaner directory. Thanks!
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?