-
Notifications
You must be signed in to change notification settings - Fork 8
Module Resolution Failing #205
Comments
Further to this I modded the TsMain class and provided my own compiler host as per the example here: https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API#customizing-module-resolution I then setup the resolveModuleNames function to resolve my project root'ed modules correctly. This seemed to work however I now have the following output:
|
Sorry for the long reply, Brad. I was away, but now I'm back. Thanks for your feedback and for opening this issue. I opened up a couple of issues because of it. I'll reduce some of the noise in the log messages and investigate the error you're having. The part of the code that's throwing that error actually won't exist in the next minor revision, but I'll take a look to try to figure out why it was occurring to see if I'll need to fix the new code. |
Cheers @dsherret looking forward to the updates. If I can be of any further assistance let me know. |
@brad-jones I'm working on #208, which will allow me to more easily do that. I'm separating the definitions, writing and code generation, from the typescript compiler part of this library. Not sure how long it will take because I'm doing a major internal code refactoring to clean up some of the mess and simplify a few things. |
Using this package out of the box, without any custom compiler options I get the following error:
On inspection of the stack trace, it is failing where it hits the class that "Foo" extends because it has not been able to resolve the imported parent class.
The TsNode contains:
I then attempted to provide my compiler options from my tsconfig.json file.
They look like this:
NOTE: I cast the CompilerOptions to to get them passed through.
After I did this I then got the following exception:
As you might have already worked out I have setup my environment to be able to require from the project root. This tsconfig.json works just fine in atom-typescript. ie: Atom resolves
app/Contracts/IFoo
without compliant. It would seem though that the baseUrl & paths properties are not being taken into to consideration when calling your reflection lib.The text was updated successfully, but these errors were encountered: