fix!: rename the _fresh build folder to .fresh (BREAKING)
As mentioned in a prior discussion, it seemed like renaming _fresh build folder to .fresh would align more with generated files than the current _. This PR implements that suggestion, to make the breaking change potentially sooner rather than later.
Prior arts
node_modules/.deno- Deno installed packages.vite- Cache of prebuilt packages and files.angular- Cache of built files and metadata.github/or.vscode/folders
The . prefix in general seems to be used either for generated files, files that should be considered "hidden", or configuration files (e.g. .editorconfig or .gitignore). This seems to fit well with outDir, and would make naming more consistent IMO.
I strongly object to this. .fresh is a hidden folder, those usually reserved for configuration files or ephemeral caches.
Generated output should be visible in a clearly marked/named folder. Common folder names are:
distoutbuildpublic(that may clash withstatica bit)
The examples also are not fitting IMHO:
node_modules/.deno` is a special case, it's wild west inside that hierarchy.vite/.angularare cache/staging folders, not generated output. Cache/staging folders are ephemeral, those can be deleted without any side effect, unlike generated output folders, which might break a running site.github/.vscodeare well-known special purpose configuration folders
If no agreement on a new folder name for the generated output can be reached, please keep the _fresh name, it is at least not a hidden folder.