Custom auto generated path in jsconfig based on custom alias

[DouglasCalora]

Quasar apparently automatically generates the paths of the aliases created in quasar.config.js in .quasar and I just need to extend it in my jsconfig.json. However, there are aliases created by my quasar-app-extension that are not declared in my quasar.config.js and the paths are not generated automatically, and I cannot merge the use of custom path + extends in my jsconfig.json

This not works:

{
  "compilerOptions": {
    "paths": {
      "asteroid": [
        "/node_modules/@bildvitta/quasar-ui-asteroid/src/asteroid.js"
      ]
    }
  },
  "extends": "./.quasar/tsconfig.json"
}

It's only work the 'asteroid' path and the paths generated by quasar are overwritten.

[yusufkandemir]

It's due to how tsconfig/jsconfig works. You can use quasar.config file > build > typescript > extendTsConfig: https://quasar.dev/quasar-cli-vite/supporting-ts#quasar-config-ts
It affects .quasar/tsconfig.json. So, it would work fine when using JS as well.

This should work:

extendTsConfig(tsConfig) {
  tsConfig.build.compilerOptions.paths = {
    ...tsConfig.build.compilerOptions.paths,
    asteroid: ['/node_modules/@bildvitta/quasar-ui-asteroid/src/asteroid.js']
  }
}