/home/techb158/balavpn.abdallabala.com/node_modules/next/dist/build/webpack
NameSizeModeActions
alias/-0777rm
config/-0777rm
loaders/-0777rm
plugins/-0777rm
cache-invalidation.d.ts7830666editdlrm
cache-invalidation.js34620666editdlrm
cache-invalidation.js.map48310666editdlrm
stringify-request.d.ts1460666editdlrm
stringify-request.js4410666editdlrm
stringify-request.js.map6970666editdlrm
utils.d.ts9100666editdlrm
utils.js44800666editdlrm
utils.js.map71620666editdlrm
Edit: /home/techb158/balavpn.abdallabala.com/node_modules/next/dist/build/webpack/cache-invalidation.d.ts (783B)
/** * Atomically write an invalidation marker. * * Because attempting to delete currently open cache files could cause issues, * actual deletion of files is deferred until the next start-up (in * `checkPersistentCacheInvalidationAndCleanup`). * * In the case that no database is currently open (e.g. via a separate CLI * subcommand), you should call `cleanupPersistentCache` *after* this to eagerly * remove the cache files. */ export declare function invalidatePersistentCache(cacheDirectory: string): Promise; /** * Called during startup. See if the cache is in a partially-completed * invalidation state. Finds and delete any invalidated cache files. */ export declare function checkPersistentCacheInvalidationAndCleanup(cacheDirectory: string): Promise;