Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[TASK] Avoid double-terse in incremental builds via
grunt scripts
Ensure `grunt build` generates a timestamp in Build/.cache/grunt-newer/terser/typescript/timestamp by using `newer:terser:typescript` instead of `terser:typescript`. This is for `grunt newer:terser:typescript` (as executed by `grunt scripts`) to able to pick this timestamp in subsequent builds to avoid re-tersing files that have already been tersed in a previous full-run (grunt build). Background: With the changes in #95016, `grunt terser:typescript` became a static task that executed terser for all typescript files in Build/JavaScript/. Prior to that change the list of files to be tersed was dynamically configured only for changed files in `grunt copy:ts_files`. Now, that means `grunt newer:copy:ts_files terser:typescript` was equal to `grunt newer:copy:ts_files newer:terser:typescript`. That changed with #95015 because `grunt build` creates a cache for incremental builds of tsc but not for newer:terser. Note: Using newer: during `grunt build` has no impact on which files are processed as `grunt build` cleans all cache files upfront and therefore `newer:terser:typescript` will terse all files in that context and only creates the timestamp additionally. Releases: master Resolves: #95341 Related: #95016 Change-Id: I90b74198f8982012935d86db94f8e1e71fedc548 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71226 Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by: core-ci <typo3@b13.com> Tested-by: Benni Mack <benni@typo3.org> Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by: Benni Mack <benni@typo3.org>
- Loading branch information