Dec 27, 2013 at 3:59 PM
Edited Dec 27, 2013 at 4:46 PM
I recently updated my project from 0.8.3 to 0.9.5. I am compiling to ES3 and using AMD. I do not combine the JS into a single file. At development time I load the modules dynamically using RequireJS. At compile time I use the RequireJS optimizer for single
After refactoring a few things I am stuck at two distinct errors (several occurrences).
Module cannot be aliased to a non-module type.
Unable to resolve external module '...'
I have 84 typescript files and 21 definition files in my project. When using the node compiler I am able to pass in all 105 ts/d.ts files in
and it compiles the JS for each without any errors or warnings. However, when I only specific a single ts file with the node compiler I am able to see the same module import errors that VS shows.
I read about
but I'm not sure that will help me in my scenario as it reads like it will only be used when using the
I compared my
with a basic HTML TypeScript application one and I noticed that mine has several
entries that new typescript project does not (see below). I'm not sure if these are harmful or not. My project type is a Class Library but I correctly setup the TypeScript Build settings tab as well as Tools->Options->Text Editor->TypeScript->Project.
I want to take advantage of VS's error reporting but I am unsure how to resolve these errors at this point. Any suggestions are appreciated