fix!: rename the _fresh build folder to .fresh (BREAKING) #3175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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/
foldersThe
.
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 withoutDir
, and would make naming more consistent IMO.