Bump the development-dependencies group across 1 directory with 4 updates

[dependabot]

Bumps the development-dependencies group with 4 updates in the / directory: @microsoft/api-extractor, @testing-library/jest-dom, @playwright/test and @types/lodash.

Updates @microsoft/api-extractor from 7.43.1 to 7.43.2

Changelog

Sourced from @​microsoft/api-extractor's changelog.

7.43.2

Mon, 06 May 2024 15:11:04 GMT

Version update only

Commits

• ac21ee9 Bump versions [skip ci]
• 04e4984 Update changelogs [skip ci]
• See full diff in compare view

Updates @testing-library/jest-dom from 6.4.2 to 6.4.5

Release notes

Sourced from @​testing-library/jest-dom's releases.

v6.4.5

6.4.5 (2024-05-03)

Bug Fixes

• add js suffix to isEqualWith import (#599) (e8c8b13)

v6.4.4

6.4.4 (2024-05-03)

Bug Fixes

• infra: codecoverage token addition (#600) (f03a582)

v6.4.3

6.4.3 (2024-05-03)

Bug Fixes

• Updates role support for aria-required attribute in toBeRequired (#590) (20aca33)

Commits

• e8c8b13 fix: add js suffix to isEqualWith import (#599)
• f03a582 fix(infra): codecoverage token addition (#600)
• 20aca33 fix: Updates role support for aria-required attribute in toBeRequired (#590)
• bd82f64 refactor: replace lodash with own implementation when possible (#593)
• See full diff in compare view

Updates @playwright/test from 1.43.1 to 1.44.0

Release notes

Sourced from @​playwright/test's releases.

v1.44.0

New APIs

Accessibility assertions

• expect(locator).toHaveAccessibleName() checks if the element has the specified accessible name:

  const locator = page.getByRole('button');
  await expect(locator).toHaveAccessibleName('Submit');

• expect(locator).toHaveAccessibleDescription() checks if the element has the specified accessible description:

  const locator = page.getByRole('button');
  await expect(locator).toHaveAccessibleDescription('Upload a photo');

• expect(locator).toHaveRole() checks if the element has the specified ARIA role:

  const locator = page.getByTestId('save-button');
  await expect(locator).toHaveRole('button');

Locator handler

• After executing the handler added with page.addLocatorHandler(), Playwright will now wait until the overlay that triggered the handler is not visible anymore. You can opt-out of this behavior with the new noWaitAfter option.
• You can use new times option in page.addLocatorHandler() to specify maximum number of times the handler should be run.
• The handler in page.addLocatorHandler() now accepts the locator as argument.
• New page.removeLocatorHandler() method for removing previously added locator handlers.

const locator = page.getByText('This interstitial covers the button');
await page.addLocatorHandler(locator, async overlay => {
  await overlay.locator('#close').click();
}, { times: 3, noWaitAfter: true });
// Run your tests that can be interrupted by the overlay.
// ...
await page.removeLocatorHandler(locator);

Miscellaneous options

• multipart option in apiRequestContext.fetch() now accepts FormData and supports repeating fields with the same name.

  const formData = new FormData();
  formData.append('file', new File(['let x = 2024;'], 'f1.js', { type: 'text/javascript' }));
  formData.append('file', new File(['hello'], 'f2.txt', { type: 'text/plain' }));
  context.request.post('https://example.com/uploadFiles', {
    multipart: formData

... (truncated)

Commits

• a6aa50b chore: set version to 1.44.0 (#30680)
• 54c157d cherry-pick(#30677): chore: print resolved host in the http server te… (#30679)
• 2d437e8 cherry-pick(#30646): feat(chromium): roll to r1117 (#30652)
• 7637399 cherry-pick(#30636): fix(role): extract tagName safely (#30639)
• 9e091e7 cherry-pick(#30611): chore: add common env vars for junit and json re… (#30624)
• 154694b chore: update playwright-browsers to Mar 19 (#30599)
• fa7d4e5 docs: releae notes 1.44 for js (#30596)
• b9f70f4 docs(junit): document existing options and env (#30595)
• fb90797 fix(last-run): remove globalOutputDir (#30571)
• 96f3d19 feat(ctrl_or_meta): add a universal ctrl-meta modifier (#30572)
• Additional commits viewable in compare view

Updates @types/lodash from 4.17.0 to 4.17.1

Commits

• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8acba30

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR