Open mgs95 opened 4 years ago
Typescript users use a tsconfig.json file instead of a jsconfig.json file. Both contain the include field which is used to get the absolute path.
tsconfig.json
jsconfig.json
include
Inside resolveImportPath.js there should be something like this:
resolveImportPath.js
var jsconfigPath = path.resolve(CMD, 'jsconfig.json'); var tsconfigPath = path.resolve(CMD, 'tsconfig.json'); var jsconfigInclude; if (fs.existsSync(jsconfigPath) || fs.existsSync(tsconfigPath)) { var config = fs.readFileSync(jsconfigPath, 'utf8') || fs.readFileSync(tsconfigPath, 'utf8'); var jsconfig = JSON.parse(config); jsconfigInclude = jsconfig.include ? jsconfig.include[0] : null; }
With this fix, issues regarding absolute paths should be resolved.
I have the same problem.
Thanks for the solution @mgs95
Typescript users use a
tsconfig.json
file instead of ajsconfig.json
file. Both contain theinclude
field which is used to get the absolute path.Inside
resolveImportPath.js
there should be something like this:With this fix, issues regarding absolute paths should be resolved.