resolve.cachePredicate : () => boolean (enhanced-resolve) mismatch type declaration about reboost HOT 5 CLOSED

I think I have resolved it in another way

from reboost.

Same problem for the following enhanced-resolve options:

cacheWithContext: boolean
conditionNames: string[]
fileSystem: any
fullySpecified: boolean
resolver: undefined
resolveToContext: boolean
unsafeCache: boolean

from reboost.

Well, I can't say if it's actually an issue. If you see https://github.com/sarsamurmu/reboost/blob/primary/packages/core/src/node/index.ts#L137, I have intentionally disabled them for general users. Do you think we should enable them?

from reboost.

Documentation mentions that:

resolve

Type: object

Configurations for module and file resolving. Because it uses enhanced-resolve, it supports all of its options. enhanced-resolve is also used by webpack, so you may be already familiar with these options.

I strongly believe that consistency between documentation and implementation is of utmost importance!

from reboost.

I suggest to do the same for the contentServer as regards koa-static (koa-send) and, of course, http-proxy and chokidar.

from reboost.