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.
Updated all direct npm dependencies to
@latest
.Observed changes:
trailingComma
to"all"
prettier/prettier#11479marked
now omitsid
attributes for header tags (confirmed benign) fix: change defaults for mangle and headerIds to false markedjs/marked#2890esbuild
.I was really hoping this would be a trivial process, but sadly it wasn't. For posterity, here's what the process ended up being:
Ran
./build.py
to confirm the repo still built, discovered formatting changes.To reformat with new Prettier defaults:
Since we pulled a lot of JS tooling updates, I ran a quick script to save the built artifacts so I could diff the JS output:
Ran this script first on
main
, then with the updatedpackage.json
&package-lock.json
. Usedgit
to diff thebaseline-compare
changes. Confirmed they looked harmless.