Computing buildInfoTime even when !isIncremental
#60.500 aberto em 14 de nov. de 2024
Métricas do repositório
- Stars
- (48.455 stars)
- Métricas de merge de PR
- (Mesclagem média 6d 17h) (9 fundiu PRs em 30d)
Description
@sheetalkamat @johnnyreilly I'm out of my depth, but I think there's maybe a bug introduced here.
I'm getting
TypeError: Cannot read properties of undefined (reading 'includes')in fork-ts-checker-webpack-plugin when my project is NOTincremental: true.Prior to this revision
buildInfoTimewas not computed ifbuildInfoPathwasundefinedbut after this change, even thoughbuildInfoPathis undefined, it is still attempting to computets_getModifiedTime(host, buildInfoPath)Eventually, this calls to
isArtifact(undefined)in fork-ts-checker-webpack-plugin\lib\typescript\worker\lib\system.js[function isArtifact(path) {
return ((artifacts.dirs.some((dir) => path.includes(dir)) || artifacts.files.some((file) => path === file)) && artifacts.extensions.some((extension) => path.endsWith(extension)));Perhaps this needs to be handled in fork-ts-checker-webpack-plugin? But it seems to me that perhaps
buildInfoTimecould be skipped whenbuildInfoPathis unavailable.
Originally posted by @JasonKleban in dca9182