Skip to content

fix: handle undefined paths in getModifiedTime#865

Open
mogzol wants to merge 1 commit intoTypeStrong:mainfrom
mogzol:main
Open

fix: handle undefined paths in getModifiedTime#865
mogzol wants to merge 1 commit intoTypeStrong:mainfrom
mogzol:main

Conversation

@mogzol
Copy link

@mogzol mogzol commented May 21, 2025

Fixes #855

When building projects in tsc build mode (with typescript.build set to true), some paths passed to getModifiedTime will be undefined. Previously, this would cause an error and prevent type-checking (see #855). With these changes, the modified time will just be returned as undefined in such cases, which allows type checking to complete successfully.

When building projects in `tsc` build mode (with `typescript.build` set
to `true`), some paths passed to `getModifiedTime` will be `undefined`.
Previously, this would cause an error and prevent type-checking (see
TypeStrong#855).
With these changes, the modified time will just be returned as
`undefined` in such cases, which allows type checking to complete
successfully.
@develra
Copy link

develra commented Aug 12, 2025

+1 - can we get a maintainer to look at this PR? I also just ran into this issue when trying to upgrade typescript. Work around seems reasonable to me.

@bkw
Copy link

bkw commented Feb 23, 2026

Is this project still alive?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Type Checking Not Works with TypeScript 5.6+ and build: true Option

3 participants