If we think it's important to print a status message, I'd rather add a new one explaining that it's being forced.

Not able to comment at location but you can put !force flag in addition here as well

// Check oldest output file name only if there is no missing output file name
                if (!missingOutputFileName) {
                    // If the upstream project's newest file is older than our oldest output, we
                    // can't be out of date because of it
                    if (refStatus.newestInputFileTime && refStatus.newestInputFileTime <= oldestOutputFileTime) {
                        continue;
                    }
                    // If the upstream project has only change .d.ts files, and we've built
                    // *after* those files, then we're "psuedo up to date" and eligible for a fast rebuild
                    if (refStatus.newestDeclarationFileContentChangedTime && refStatus.newestDeclarationFileContentChangedTime <= oldestOutputFileTime) {
                        pseudoUpToDate = true;
                        upstreamChangedProject = ref.path;
                        continue;
                    }
                    // We have an output older than an upstream output - we are out of date
                    Debug.assert(oldestOutputFileName !== undefined, "Should have an oldest output filename here");
                    return {
                        type: UpToDateStatusType.OutOfDateWithUpstream,
                        outOfDateOutputFileName: oldestOutputFileName,
                        newerProjectName: ref.path
                    };
                }

I expected that to be undefined since the previous !force check would prevent it from being set. Would you like me to add an assert?

Hmm for some reason i think it will be evaluated because missingOutputFileName is going to be undefined? as we are not doing those checks any more. assert would be nice if thats not the case

Hmm for some reason i think it will be evaluated because missingOutputFileName is going to be undefined? as we are not doing those checks any more. assert would be nice if thats not the case

I think this is your way of telling me I read it backwards. 😄

Edit: Turns out it wasn't asserting because oldestOutputFileTime was set to max-date so the if before the assert was true, causing it to be skipped. Obviously, checking explicitly is better.