Webpack Persistent Cache Permission Validation After Backup Restoration

Goal: Determine whether webpack’s persistent cache remains usable after a project backup is restored on a system where the node_modules/.cache/webpack directory may have different ownership or permission bits.

Uncertainty: The webpack documentation does not define a required permission mask or ownership for the cache directory, so it is unclear which specific filesystem access rights (read, write, execute) webpack checks when deciding to reuse cached entries after restoration.

Questions: What minimum permissions must the cache directory have for webpack to treat it as valid? Does webpack verify both readability and writability, or only readability? How does webpack behave when the directory is readable but lacks write permission for the Node.js process?