Custom auto generated path in jsconfig based on custom alias #18029
Unanswered
DouglasCalora
asked this question in
CLI - PWA mode
Replies: 1 comment
-
It's due to how tsconfig/jsconfig works. You can use This should work: extendTsConfig(tsConfig) {
tsConfig.build.compilerOptions.paths = {
...tsConfig.build.compilerOptions.paths,
asteroid: ['/node_modules/@bildvitta/quasar-ui-asteroid/src/asteroid.js']
}
} |
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Quasar apparently automatically generates the paths of the aliases created in
quasar.config.js
in.quasar
and I just need to extend it in myjsconfig.json
. However, there are aliases created by myquasar-app-extension
that are not declared in myquasar.config.js
and the paths are not generated automatically, and I cannot merge the use of custom path + extends in myjsconfig.json
This not works:
It's only work the 'asteroid' path and the paths generated by quasar are overwritten.
Beta Was this translation helpful? Give feedback.
All reactions