Update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@electron-forge/cli	6.0.0-beta.61 -> 6.0.0-beta.63
@electron-forge/maker-deb	6.0.0-beta.61 -> 6.0.0-beta.63
@electron-forge/maker-dmg	6.0.0-beta.61 -> 6.0.0-beta.63
@electron-forge/maker-rpm	6.0.0-beta.61 -> 6.0.0-beta.63
@electron-forge/maker-squirrel	6.0.0-beta.61 -> 6.0.0-beta.63
@electron-forge/maker-zip	6.0.0-beta.61 -> 6.0.0-beta.63
@electron-forge/plugin-webpack	6.0.0-beta.61 -> 6.0.0-beta.63
@fontsource/inter	4.5.1 -> 4.5.4
@fortawesome/fontawesome-svg-core (source)	1.2.36 -> 1.3.0
@fortawesome/react-fontawesome	0.1.16 -> 0.1.17
@playwright/test (source)	1.17.1 -> 1.19.2
@popperjs/core	2.11.0 -> 2.11.2
@reduxjs/toolkit (source)	1.6.2 -> 1.8.0
@swc/core (source)	1.2.118 -> 1.2.147
@types/cytoscape	3.19.2 -> 3.19.4
@types/lodash-es	4.17.5 -> 4.17.6
@types/node	16.11.11 -> 16.11.26
@types/nodegit	0.27.6 -> 0.27.10
@types/react	17.0.37 -> 17.0.39
@types/react-dom	17.0.11 -> 17.0.12
@types/react-redux	7.1.20 -> 7.1.23
@types/styled-components	5.1.16 -> 5.1.24
@typescript-eslint/eslint-plugin	5.5.0 -> 5.13.0
@typescript-eslint/parser	5.5.0 -> 5.13.0
adm-zip	0.5.4 -> 0.5.9
css-loader	6.5.1 -> 6.6.0
cytoscape (source)	3.20.0 -> 3.21.0
date-fns	2.27.0 -> 2.28.0
dotenv-webpack	7.0.3 -> 7.1.0
electron	16.0.4 -> 16.0.10
eslint (source)	8.6.0 -> 8.10.0
eslint-plugin-react	7.28.0 -> 7.29.2
history	5.1.0 -> 5.3.0
mini-css-extract-plugin	2.4.5 -> 2.5.3
node-fetch	3.1.0 -> 3.2.1
nodegit (source)	0.28.0-alpha.10 -> 0.28.0-alpha.11
playwright (source)	1.17.1 -> 1.19.2
react-router-dom	6.2.1 -> 6.2.2
react-select	5.2.1 -> 5.2.2
react-spring	9.3.3 -> 9.4.3
stream-chain	2.2.4 -> 2.2.5
typescript (source)	4.5.2 -> 4.6.2

---

Release Notes

electron-userland/electron-forge

v6.0.0-beta.63

Compare Source

Bug Fixes

• cli: re-add shebang to electron-forge binary (#​2671) (1ca418ec)

v6.0.0-beta.62

Compare Source

New Features

• publisher-github: add retry support (#​2550) (a400066d)

Bug Fixes

• replace colors with chalk (#​2666) (e909ae83)
• plugin-webpack:
  • rebuild native modules before packaging (#​2584) (21310bbf)
  • validate that the correct entry point is used (#​2522) (3de904b6)

FortAwesome/Font-Awesome

v1.3.0

FortAwesome/react-fontawesome

v0.1.17

Compare Source

Added

• New v6 sizes and animations

---

Microsoft/playwright

v1.19.2

Compare Source

Highlights

This patch includes the following bug fixes:

https://github.com/microsoft/playwright/issues/12091 - [BUG] playwright 1.19.0 generates more than 1 trace file per testhttps://github.com/microsoft/playwright/issues/121066 - [BUG] Error: EBUSY: resource busy or locked when using volumes in docker-compose with playwright 1.19.0 and mcr.microsoft.com/playwright:v1.15.0-focal

Browser Versions

• Chromium 100.0.4863.0
• Mozilla Firefox 96.0.1
• WebKit 15.4

This version was also tested against the following stable channels:

• Google Chrome 98
• Microsoft Edge 98

v1.19.1

Compare Source

Highlights

This patch includes the following bug fixes:

https://github.com/microsoft/playwright/issues/12075 - [Question] After update to 1.19 firefox fails to runhttps://github.com/microsoft/playwright/issues/120900 - [BUG] did something change on APIRequest/Response APIs ?

Browser Versions

• Chromium 100.0.4863.0
• Mozilla Firefox 96.0.1
• WebKit 15.4

This version was also tested against the following stable channels:

• Google Chrome 98
• Microsoft Edge 98

v1.19.0

Compare Source

Version 1.19

Playwright Test Updates

Soft assertions

Playwright Test v1.19 now supports soft assertions. Failed soft assertions do not terminate test execution, but mark the test as failed. Read more in our documentation.

// Make a few checks that will not stop the test when failed...
await expect.soft(page.locator('#status')).toHaveText('Success');
await expect.soft(page.locator('#eta')).toHaveText('1 day');

// ... and continue the test to check more things.
await page.locator('#next-page').click();
await expect.soft(page.locator('#title')).toHaveText('Make another order');

Custom error messages

You can now specify a custom error message as a second argument to the expect and expect.soft functions, for example:

await expect(page.locator('text=Name'), 'should be logged in').toBeVisible();

The error would look like this:

    Error: should be logged in

    Call log:
      - expect.toBeVisible with timeout 5000ms
      - waiting for selector "text=Name"

      2 |
      3 | test('example test', async({ page }) => {
    > 4 |   await expect(page.locator('text=Name'), 'should be logged in').toBeVisible();
        |                                                                  ^
      5 | });
      6 |

Parallel mode in file

By default, tests in a single file are run in order. If you have many independent tests in a single file, you can now
run them in parallel with method: test.describe.configure:

import { test } from '@​playwright/test';

test.describe.configure({ mode: 'parallel' });

test('parallel 1', async () => {});
test('parallel 2', async () => {});

⚠️ Potentially breaking change in Playwright Test Global Setup

It is unlikely that this change will affect you, no action is required if your tests keep running as they did.

We've noticed that in rare cases, the set of tests to be executed was configured in the global setup by means of the environment variables. We also noticed some applications that were post processing the reporters' output in the global teardown. If you are doing one of the two, learn more

Locator Updates

Locator now supports a has option that makes sure it contains another locator inside:

await page.locator('article', {
  has: page.locator('.highlight'),
}).locator('button').click();

The snippet above will select article that has highlight in it and will press the button in it.
Read more in locator documentation

Other Updates

• New method: Locator.page
• method: Page.screenshot and method: Locator.screenshot now automatically hides blinking caret
• Playwright Codegen now generates locators and frame locators
• New option url in testConfig.webServer to ensure your web server is ready before running the tests
• New property: TestInfo.errors and property: TestResult.errors that contain all failed assertions and soft assertions.

Browser Versions

• Chromium 100.0.4863.0
• Mozilla Firefox 96.0.1
• WebKit 15.4

This version was also tested against the following stable channels:

• Google Chrome 98
• Microsoft Edge 98

---

v1.18.1

Compare Source

Highlights

This patch includes improvements to the TypeScript support and the following bug fixes:

https://github.com/microsoft/playwright/issues/11550 - [REGRESSION]: Errors inside route handler does not lead to unhandled rejections anymorehttps://github.com/microsoft/playwright/issues/115522 - [BUG] Could not resolve "C:\repo\framework\utils" in file C:\repo\tests\test.ts.

Browser Versions

• Chromium 99.0.4812.0
• Mozilla Firefox 95.0
• WebKit 15.4

This version was also tested against the following stable channels:

• Google Chrome 97
• Microsoft Edge 97

v1.18.0

Compare Source

Locator Improvements

• [locator.dragTo(locator)][locator.dragTo(locator)]
• [expect(locator).toBeChecked({ checked })][expect(locator).toBeChecked({ checked })]
• Each locator can now be optionally filtered by the text it contains:

  await page.locator('li', { hasText: 'my item' }).locator('button').click();

  Read more in locator documentation.

Testing API improvements

• [expect(response).toBeOK()][expect(response).toBeOK()]
• [testInfo.attach()][testInfo.attach()]
• [test.info()][test.info()]

Improved TypeScript Support

1. Playwright Test now respects tsconfig.json's baseUrl and paths, so you can use aliases
2. There is a new environment variable PW_EXPERIMENTAL_TS_ESM that allows importing ESM modules in your TS code, without the need for the compile step. Don't forget the .js suffix when you are importing your esm modules. Run your tests as follows:

npm i --save-dev @​playwright/test@1.18.0
PW_EXPERIMENTAL_TS_ESM=1 npx playwright test

Create Playwright

The npm init playwright command is now generally available for your use:

### Run from your project's root directory
npm init playwright
### Or create a new project
npm init playwright new-project

This will scaffold everything needed to get started with Playwright Test: configuration file, optionally add examples, a GitHub Action workflow and a first test example.spec.ts.

New APIs & changes

• new [testCase.repeatEachIndex][testCase.repeatEachIndex] API
• [acceptDownloads][acceptDownloads] option now defaults to true

Breaking change: custom config options

Custom config options are a convenient way to parametrize projects with different values. Learn more in the parametrization guide.

Previously, any fixture introduced through [test.extend][test.extend] could be overridden in the [testProject.use][testProject.use] config section. For example,

// WRONG: THIS SNIPPET DOES NOT WORK SINCE v1.18.

// fixtures.js
const test = base.extend({
  myParameter: 'default',
});

// playwright.config.js
module.exports = {
  use: {
    myParameter: 'value',
  },
};

The proper way to make a fixture parametrized in the config file is to specify option: true when defining the fixture. For example,

// CORRECT: THIS SNIPPET WORKS SINCE v1.18.

// fixtures.js
const test = base.extend({
  // Fixtures marked as "option: true" will get a value specified in the config,
  // or fallback to the default value.
  myParameter: ['default', { option: true }],
});

// playwright.config.js
module.exports = {
  use: {
    myParameter: 'value',
  },
};

Browser Versions

• Chromium 99.0.4812.0
• Mozilla Firefox 95.0
• WebKit 15.4

This version was also tested against the following stable channels:

• Google Chrome 97
• Microsoft Edge 97

---

(1.18.0-beta-1642620709000)

v1.17.2

Compare Source

Bugfixes

#​11274 - fix: pin colors to 1.4.0
#​11228 - fix(click): don't fail on stale context while click

popperjs/popper-core

v2.11.2

Compare Source

v2.11.1

Compare Source

Note: 2.11.1 has a wrong dependency in its package.json, 2.11.2 was released to fix it

Bug Fixes

• Round computed offsets after all the modifiers math is executed (#​1418)

• Fix regression with detection of clipping boundaries (#​1478)

reduxjs/redux-toolkit

v1.8.0

Compare Source

This release adds the new "listener" middleware, updates configureStore's types to better handle type inference from middleware that override dispatch return values, and updates our TS support matrix to drop support for TS < 4.1.

Changelog

New "Listener" Side Effects Middleware

RTK has integrated the thunk middleware since the beginning. However, thunks are imperative functions, and do not let you run code in response to dispatched actions. That use case has typically been covered with libraries like redux-saga (which handles side effects with "sagas" based on generator functions), redux-observable (which uses RxJS observables), or custom middleware.

We've added a new "listener" middleware to RTK to cover that use case. The listener middleware is created using createListenerMiddleware(), and lets you define "listener" entries that contain an "effect" callback with additional logic and a way to specify when that callback should run based on dispatched actions or state changes.

Conceptually, you can think of this as being similar to React's useEffect hook, except that it runs logic in response to Redux store updates instead of component props/state updates.

The listener middleware is intended to be a lightweight alternative to more widely used Redux async middleware like sagas and observables. While similar to thunks in level of complexity and concept, it can replicate some common saga usage patterns. We believe that the listener middleware can be used to replace most of the remaining use cases for sagas, but with a fraction of the bundle size and a much simpler API.

Listener effect callbacks have access to dispatch and getState, similar to thunks. The listener also receives a set of async workflow functions like take, condition, pause, fork, and unsubscribe, which allow writing more complex async logic.

Listeners can be defined statically by calling listenerMiddleware.startListening() during setup, or added and removed dynamically at runtime with special dispatch(addListener()) and dispatch(removeListener()) actions.

The API reference is available at:

https://redux-toolkit.js.org/api/createListenerMiddleware

Huge thanks to @​FaberVitale for major contributions in refining the middleware API and implementing key functionality.

Basic usage of the listener middleware looks like:

import { configureStore, createListenerMiddleware } from '@​reduxjs/toolkit'

import todosReducer, {
  todoAdded,
  todoToggled,
  todoDeleted,
} from '../features/todos/todosSlice'

// Create the middleware instance and methods
const listenerMiddleware = createListenerMiddleware()

// Add one or more listener entries that look for specific actions.
// They may contain any sync or async logic, similar to thunks.
listenerMiddleware.startListening({
  actionCreator: todoAdded,
  effect: async (action, listenerApi) => {
    // Run whatever additional side-effect-y logic you want here
    console.log('Todo added: ', action.payload.text)

    // Can cancel other running instances
    listenerApi.cancelActiveListeners()

    // Run async logic
    const data = await fetchData()

    // Pause until action dispatched or state changed
    if (await listenerApi.condition(matchSomeAction)) {
      // Use the listener API methods to dispatch, get state,
      // unsubscribe the listener, start child tasks, and more
      listenerApi.dispatch(todoAdded('Buy pet food'))
      listenerApi.unsubscribe()
    }
  },
})

const store = configureStore({
  reducer: {
    todos: todosReducer,
  },
  // Add the listener middleware to the store.
  // NOTE: Since this can receive actions with functions inside,
  // it should go before the serializability check middleware
  middleware: (getDefaultMiddleware) =>
    getDefaultMiddleware().prepend(listenerMiddleware.middleware),
})

You can use it to write more complex async workflows, including pausing the effect callback until a condition check resolves, and forking "child tasks" to do additional work:

// Track how many times each message was processed by the loop
const receivedMessages = {
  a: 0,
  b: 0,
  c: 0,
}

const eventPollingStarted = createAction('serverPolling/started')
const eventPollingStopped = createAction('serverPolling/stopped')

listenerMiddleware.startListening({
  actionCreator: eventPollingStarted,
  effect: async (action, listenerApi) => {
    // Only allow one instance of this listener to run at a time
    listenerApi.unsubscribe()

    // Start a child job that will infinitely loop receiving messages
    const pollingTask = listenerApi.fork(async (forkApi) => {
      try {
        while (true) {
          // Cancellation-aware pause for a new server message
          const serverEvent = await forkApi.pause(pollForEvent())
          // Process the message. In this case, just count the times we've seen this message.
          if (serverEvent.type in receivedMessages) {
            receivedMessages[
              serverEvent.type as keyof typeof receivedMessages
            ]++
          }
        }
      } catch (err) {
        if (err instanceof TaskAbortError) {
          // could do something here to track that the task was cancelled
        }
      }
    })

    // Wait for the "stop polling" action
    await listenerApi.condition(eventPollingStopped.match)
    pollingTask.cancel()
  },
})

configureStore Middleware Type Improvements

Middleware can override the default return value of dispatch. configureStore tries to extract any declared dispatch type overrides from the middleware array, and uses that to alter the type of store.dispatch.

We identified some cases where the type inference wasn't working well enough, and rewrote the type behavior to be more correct.

TypeScript Support Matrix Updates

RTK now requires TS 4.1 or greater to work correctly, and we've dropped 4.0 and earlier from our support matrix.

Other Changes

The internal logic for the serializability middleware has been reorganized to allow skipping checks against actions, while still checking values in the state.

What's Changed

Since most of the implementation work on the middleware was done over the last few months, this list only contains the most recent PRs since 1.7.2. For details on the original use case discussions and the evolution of the middleware API over time, see:

• RTK issue #​237: Add an action listener middleware
• RTK PR #​547: yet another attempt at an action listener middleware
• RTK discussion #​1648: New experimental "action listener middleware" package available

PRs since 1.7.2:

• Rewrite MiddlewareArray and gDM for better Dispatch inference by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/2001
• Change listener middleware API name and signature by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/2005
• feat(alm): add cancellation message to TaskAbortError, listenerApi.signal & forkApi.signal. by @​FaberVitale in https://github.com/reduxjs/redux-toolkit/pull/2023
• [fix][1.8.0-integration][alm]: missing type export by @​FaberVitale in https://github.com/reduxjs/redux-toolkit/pull/2026
• [chore][1.8.0-integration][alm]: apply alm breaking API changes to counter-example by @​FaberVitale in https://github.com/reduxjs/redux-toolkit/pull/2025
• Reorganize serializable check conditions by @​msutkowski in https://github.com/reduxjs/redux-toolkit/pull/2000
• fix(alm): prevent zombie listeners caused by forked tasks by @​FaberVitale in https://github.com/reduxjs/redux-toolkit/pull/2070
• Integrate the listener middleware into the RTK package by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/2072
• fix(alm): cancel forkApi.delay and forkApi.pause if listener is cancelled or completed by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/2074
• chore(alm): update counter example to 1.8.0 by @​FaberVitale in https://github.com/reduxjs/redux-toolkit/pull/2076
• Enable cancelling active listeners when unsubscribing by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/2078
• v1.8.0 integration by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/2024

Full Changelog: reduxjs/redux-toolkit@v1.7.2...v1.8.0

v1.7.2

Compare Source

This release fixes a TS types bug with RTK Query generated selectors, makes the RTKQ structural sharing behavior configurable, adds an option to have the serializability middleware ignore all actions, and has several minor bugfixes and enhancements to RTK Query.

Changelog

RTK Query Selector TS Types Fix

Several users had reported that as of 1.7.0 selectors generated via apiSlice.endpoint.select() were failing to compile when used, with TS errors that looked like Type '{}' is missing the following properties from type 'CombinedState<>.

We've fixed the issue, and selectors should now compile correctly when used with TS.

Additional Configuration Options

RTK Query implements a technique called "structural sharing" to preserve existing object references if possible when data for an endpoint is re-fetched. RTKQ recurses over both data structures, and if the contents appear to be the same, keeps the existing values. That helps avoid potential unnecessary re-renders in the UI, because otherwise the entire re-fetched result would be new obj

---

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.