Switching module type to system causes different compilation order

[CodySchaaf]

I'm working on switching a very large project (2500+ files) to external modules. As a first step I'm switching the module type to system so that internal and external modules can coexist (for the hopefully brief transition). My project was compiling fine before that but after changing the module type to system (from null), and the destDir option to outFile in the grunt options object, i'm getting a lot of errors.

It seems like the src order is no longer being considered. I have a list of dynamically generated top level directories that I pass into the grunt src array that specifies a general dependency order, but after making the change I''m getting ts errors that make it clear they are not being imported in the right order.

Any ideas how the compilation is different/if it is ignoring the order?

Thanks

[nycdotnet]

Hi @CodySchaaf - Sorry for not getting back to you sooner. Switching to external modules is definitely a tricky process. In general, grunt-ts should preserve the ordering identified by Grunt's glob resolution logic. If you don't believe this is the case, please post your Gruntfile, what you expect to happen, and what is happening. You might also want to try running grunt in verbose mode which should make grunt-ts repeat the command line it's using. This will let you know definitively if the compile order doesn't match your expected sequence.

Let me know if you still want to troubleshoot this, and I may be able to provide some more assistance.