We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resolveImportPath.js
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:
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.
The text was updated successfully, but these errors were encountered:
I have the same problem.
Thanks for the solution @mgs95
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
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.
The text was updated successfully, but these errors were encountered: