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
In my project, tsconfig.json with the outFile option is used. With v5.3.2, the files in the project root went first in the output file, which was exactly what is needed. But after the update, the order has changed. The files seem to be sorted by their name now, regardless their location. My project was broken, and I had to stick with 5.3.2.
So, is this an intended change?
How can I enforce the order so that the files from the root would always be first even if I switch to a newer version of grunt-ts?
Actually, in this case (when tsconfig.json exists), I think grunt-ts shouldn't have any influence on the concatenation order at all. If I run tsc directly from the command line, I get the same results as with 5.3.2.
The text was updated successfully, but these errors were encountered:
In my project,
tsconfig.json
with theoutFile
option is used. With v5.3.2, the files in the project root went first in the output file, which was exactly what is needed. But after the update, the order has changed. The files seem to be sorted by their name now, regardless their location. My project was broken, and I had to stick with 5.3.2.So, is this an intended change?
How can I enforce the order so that the files from the root would always be first even if I switch to a newer version of grunt-ts?
Actually, in this case (when tsconfig.json exists), I think grunt-ts shouldn't have any influence on the concatenation order at all. If I run
tsc
directly from the command line, I get the same results as with 5.3.2.The text was updated successfully, but these errors were encountered: