You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 4, 2021. It is now read-only.
The following patch in typescript.compile.js fixed the issue, however I think the logic is better placed in the CompilationContext
Line 74: var fileReferencesInSource = TypeScript.getReferencedFiles(sourceToParse.path, code);
// patch start
for( var i = 0; i < fileReferencesInSource.length; i++ ){
var ref = fileReferencesInSource[i];
var idx=sourceToParse.path.lastIndexOf('/');
if (idx > 0)
// prepend the path of the source file to the include
ref.path = new java.lang.String(sourceToParse.path.substring(0,idx)+'/' + ref.path);
}
// patch end
var referencedSourceUnits = compilationContext.resolveFiles(fileReferencesInSource);
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When a .ts file contains a reference in the form
the referenced file is looked up relative to the base path of the CompilationContext instead of the current source.
The text was updated successfully, but these errors were encountered: