Update devDependencies (non-major)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @testing-library/jest-dom | 6.4.0 -> 6.4.2 |
||||
| @testing-library/react | 14.1.2 -> 14.2.1 |
||||
| lint-staged | 15.2.0 -> 15.2.2 |
||||
| prettier (source) | 3.2.4 -> 3.2.5 |
||||
| stylelint (source) | 16.2.0 -> 16.2.1 |
Release Notes
testing-library/jest-dom (@testing-library/jest-dom)
v6.4.2
Bug Fixes
- Remove errant export of GetByRoleMatcher, fixing type checking in some TS configurations (#575) (a93c0c4)
v6.4.1
Bug Fixes
okonet/lint-staged (lint-staged)
v15.2.2
Patch Changes
-
#1391
fdcdad4Thanks @iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.
v15.2.1
Patch Changes
-
#1387
e4023f6Thanks @iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means thestdinof the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdinis ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.
prettier/prettier (prettier)
v3.2.5
Support Angular inline styles as single template literal (#15968 by @sosukesuzuki)
Angular v17 supports single string inline styles.
// Input
@​Component({
template: `<div>...</div>`,
styles: `h1 { color: blue; }`,
})
export class AppComponent {}
// Prettier 3.2.4
@​Component({
template: `<div>...</div>`,
styles: `h1 { color: blue; }`,
})
export class AppComponent {}
// Prettier 3.2.5
@​Component({
template: `<div>...</div>`,
styles: `
h1 {
color: blue;
}
`,
})
export class AppComponent {}
Unexpected embedded formatting for Angular template (#15969 by @JounQin)
Computed template should not be considered as Angular component template
// Input
const template = "foobar";
@​Component({
[template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}
// Prettier 3.2.4
const template = "foobar";
@​Component({
[template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}
// Prettier 3.2.5
const template = "foobar";
@​Component({
[template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}
Use "json" parser for tsconfig.json by default (#16012 by @sosukesuzuki)
In v2.3.0, we introduced "jsonc" parser which adds trialing comma by default.
When adding a new parser we also define how it will be used based on the linguist-languages data.
tsconfig.json is a special file used by TypeScript, it uses .json file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing .json file extension.
We decide to treat it as a JSON file for now to avoid the extra configuration step.
To keep using the "jsonc" parser for your tsconfig.json files, add the following to your .pretterrc file
{
"overrides": [
{
"files": ["tsconfig.json", "jsconfig.json"],
"options": {
"parser": "jsonc"
}
}
]
}
stylelint/stylelint (stylelint)
v16.2.1
- Fixed: report flags not reporting on subsequent runs when cache is used (#7483) (@ybiquitous).
- Fixed:
custom-property-no-missing-var-functionfalse positives for properties that can contain author-defined identifiers (#7478) (@ybiquitous). - Fixed:
selector-pseudo-class-no-unknownfalse positives for:seeking, the media loading state and sound state pseudo-classes (#7490) (@Mouvedia). - Fixed:
selector-max-specificityfalse positives withignoreSelectorsoption forof <selector>syntax (#7475) (@ybiquitous). - Fixed:
function-calc-no-unspaced-operatorperformance (#7505) (@ybiquitous). - Fixed:
validateOptionsto report when secondary option object is an empty object or null (#7476) (@ybiquitous). - Fixed:
report()error message responsibility for a missing node or line number (#7474) (@ybiquitous).
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
CI errors here are style related, presumably a rule changed in one of the version bumps
The JSON errors here seem to be that in a prior version the json parser preferred/added trailing commas by default, and this version switches to a style which prefers to remove them. I assume we can either accept that change and just run fix:json to get the updates, or change our config to prefer the old style if we care.
The typescript error I need to dig more on.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 85.00%. Comparing base (
86500e3) to head (0ca35e7). Report is 171 commits behind head on main.
:exclamation: Current head 0ca35e7 differs from pull request most recent head b1c168b. Consider uploading reports for the commit b1c168b to get more accurate results
Additional details and impacted files
@@ Coverage Diff @@
## main #29089 +/- ##
==========================================
- Coverage 85.01% 85.00% -0.02%
==========================================
Files 1059 1058 -1
Lines 28277 28281 +4
Branches 4538 4538
==========================================
Hits 24040 24040
- Misses 3074 3078 +4
Partials 1163 1163
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Pushed fixes for the 2 issues
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
This pull request has merge conflicts that must be resolved before it can be merged.