# Change Log ## 20.0.0 ### Major Changes - [#2688](https://github.com/toptal/davinci/pull/2688) [`bd56f8e`](https://github.com/toptal/davinci/commit/bd56f8ed767ee70126ba039cb27bb821b4689ef3) Thanks [@denieler](https://github.com/denieler)! Compile Cypress component tests with swc The engine has defaulted to swc for a while, the Cypress component config was the last place still asking for babel. Coverage was the reason it did: the istanbul instrumentation `@cypress/code-coverage` needs was wired into the babel loader only, so a repo collecting component coverage had to pay for babel to get it. The swc path instruments now, so the compiler no longer depends on `CYPRESS_COVERAGE`. - add `swc-plugin-coverage-instrument` to the swc plugins, on the loader matching project sources only. On the catch-all `.m?js` rule it fails with `failed to invoke plugin` - `createWebpackConfig` takes a new `instrumentCoverage` option, off by default. Nothing on that path reads the environment, the component config reads `CYPRESS_COVERAGE` and passes the flag - move the swc toolchain together, since wasm plugins are built against a specific `swc_core` and mixing versions fails at compile time: `@swc/core` 1.13.5 to 1.16.1 and `@swc/plugin-styled-components` 9.1.0 to 13.0.0 - component tests also get no react refresh, no `optimization`, no webpackbar, source maps off, one chunk per spec, and their own webpack cache directory. Staff Portal deleted all of that by hand after calling `createWebpackConfig` Two things to check before upgrading, both a grep away: - svg imports written as `import { ReactComponent as Icon } from './icon.svg'` are rewired by `babel-plugin-named-asset-import`, which has no swc counterpart, so a repo whose component specs render those needs its own `devServer.webpackConfig` - `grep -rn "ReactComponent as" src` - jsx string attributes written across several lines keep their newlines and indentation now, `@swc/core` 1.16.0 stopped collapsing them - `grep -rnE "\s\w[\w-]*='[^'\n]*$" src` Coverage numbers move a little as well. The two instrumenters slice statements and branches differently, so absolute counts change while percentages stay in the same range. ## 19.3.0 ### Minor Changes - [#2686](https://github.com/toptal/davinci/pull/2686) [`262f740`](https://github.com/toptal/davinci/commit/262f740aa72ff0b16c881ebb3d54cd831b20eaa0) Thanks [@denieler](https://github.com/denieler)! Stop the Cypress component dev server closing idle sockets Component specs fail intermittently with `Fetching resource at '/__cypress/src/spec-N.js' failed`, or the `ChunkLoadError: Loading chunk spec-N failed` variant depending on how the spec bundle is loaded. The spec dies before any test runs, so the run reports `0 passing`, one failing test named "An uncaught error was detected outside of a test", and a blank screenshot. The dev server is a plain Node http server, so it closes idle keep-alive sockets after Node's default 5 seconds, while Cypress reaches it through an agent that forces `keepAlive` with no free-socket timeout (`packages/network/lib/agent.ts`). A socket idle for just over 5 seconds is closed by the server while the agent still holds it, the next spec bundle request goes into a closing socket, and the proxy resets the client connection. Node's agent does not retry the way a browser does. Measured in staff-portal CI: of 697 spec transitions in the failing jobs, all 10 occurrences sit in a 5.3 to 6.4 second window between consecutive spec loads, while the 65 transitions below 5 seconds and the 452 above 6.4 seconds never failed. Spec bundle fetches are the only traffic the dev server sees, so that idle interval is exactly one spec transition, which `experimentalSingleTabRunMode` puts at 5 to 6 seconds for most specs. - raise the component dev server's `keepAliveTimeout` to 5 minutes, past the slowest spec in the sample (53 seconds), which bounds how long one socket can sit idle. Going lower is the risky direction, requests inside a single spec are milliseconds apart. `headersTimeout` is left alone, it is measured per request and does not reap idle connections (checked on Node 18, 20 and 22) - export the value as `@toptal/davinci-qa/src/configs/cypress/dev-server-keep-alive.js`, because projects that pass their own `webpackConfig` to `devServer` replace this config and have to attach it themselves: ```js import devServerKeepAlive from '@toptal/davinci-qa/src/configs/cypress/dev-server-keep-alive.js' devServer: { framework: 'react', bundler: 'webpack', webpackConfig: { ...myWebpackConfig, devServer: { server: devServerKeepAlive }, }, } ``` ## 19.2.0 ### Minor Changes - [#2681](https://github.com/toptal/davinci/pull/2681) [`9d2eb38`](https://github.com/toptal/davinci/commit/9d2eb382eb19adaa4d5ac81a9491af52dd592fff) Thanks [@denieler](https://github.com/denieler)! Upgrade `webpack-dev-server` to v5 Breaking changes: - bump `webpack-dev-server` from `^4.15.1` to `^5.2.0` in `@toptal/davinci-engine`. Options removed in v5 can no longer be passed to `davinci-engine start`, either through the `devServer` key of a project's webpack config or as CLI passthrough options. Most notably: `https` and `http2` (use `server`), `onBeforeSetupMiddleware` and `onAfterSetupMiddleware` (use `setupMiddlewares`), `magicHtml`, and `client.overlay.runtimeErrors` now defaults to `true`. See the [webpack-dev-server v5 migration guide](https://github.com/webpack/webpack-dev-server/blob/master/migration-v5.md) for the full list. - the `--https` flag of `davinci-engine start` is unaffected — it is translated to `server: 'https'`, which is the v5 API. Internal changes: - pin `@peculiar/asn1-schema` to `^2.8.0` via a root pnpm override. `webpack-dev-server` v5 generates its self-signed HTTPS certificate through `selfsigned` v5, which uses `@peculiar/x509`. The lockfile resolved two copies of `@peculiar/asn1-schema` (2.6.0 for `@peculiar/x509`, 2.8.0 for `@peculiar/asn1-x509`), and because ASN.1 schemas are registered in a module-level registry by decorators, the two instances could not see each other's registrations — `davinci-engine start --https` failed with `Cannot get schema for 'BasicConstraints' target`. Every consumer in the tree accepts `^2.8.0`, so the override deduplicates them. - widen the `@toptal/davinci-engine` peerDependency range in `@toptal/davinci-qa` from `3 - 15` to `3 - 16` to accept the new engine major. ## 19.1.0 ### Minor Changes - [#2677](https://github.com/toptal/davinci/pull/2677) [`5471216`](https://github.com/toptal/davinci/commit/547121655efc071f0c4278930f3a0b25ce0fb855) Thanks [@dulishkovych](https://github.com/dulishkovych)! Upgrade TypeScript to v5.5 and @typescript-eslint to v8 Consumers must upgrade their TypeScript version to satisfy the new peer requirement. Breaking changes: - bump the `typescript` peerDependency to `^5.5.0` (was `^4.8.4`) for `@toptal/davinci-syntax` and `@toptal/davinci-engine`. Consumers must upgrade TypeScript to 5.5 or later. - bump the `@babel/preset-typescript` peerDependency to `^7.26.0` (was `^7.17.12`) for `@toptal/davinci-storybook`. - bump `@typescript-eslint/eslint-plugin` and `@typescript-eslint/parser` from v6 to v8 in `@toptal/davinci-syntax`. - bump `eslint` peer floor from `^8.34.0` to `^8.57.0` (required by @typescript-eslint v8). - bump `eslint-plugin-jest` from v27 to v28 and `eslint-plugin-unused-imports` from v3 to v4 to align peer ranges with @typescript-eslint v8. - drop formatting rules removed in @typescript-eslint v8 (`space-before-function-paren`, `comma-dangle`, `func-call-spacing`, `member-delimiter-style`) — formatting is now deferred to Prettier, which the config already extends. - rename `@typescript-eslint/no-var-requires` → `@typescript-eslint/no-require-imports` (renamed in v8). - replace `@typescript-eslint/ban-types` with the v8 split rules (`no-empty-object-type`, `no-unsafe-function-type`, `no-wrapper-object-types`); previous allowances for `{}`, `Function`, and `object` are preserved. Internal changes: - bump `ts-jest` from `^29.1.2` to `^29.2.0`. - bump `@types/jest` from `^28.1.1` to `^29.5.0`. - set `declaration: false` in `cli-shared`, `qa`, and `storybook` tsconfig.json — these packages ship raw `.js` source and have never emitted `.d.ts` for distribution; the declaration-emit safety check no longer runs in a void. - widen the `@toptal/davinci-engine` peerDependency range in `@toptal/davinci-qa` from `3 - 14` to `3 - 15` to accept the new engine major. - update `@toptal/eslint-plugin-davinci`'s `consistent-component-props-types` rule to use `typeArguments` instead of `typeParameters` on AST references (renamed in @typescript-eslint v8). ## 19.0.0 ### Major Changes - [#2643](https://github.com/toptal/davinci/pull/2643) [`ab9666f`](https://github.com/toptal/davinci/commit/ab9666f999e7a610f6068e0145200257d8511b46) Thanks [@rocodesign](https://github.com/rocodesign)! Migrate package manager from Yarn to pnpm **WHAT (breaking change):** - switch package manager from Yarn to pnpm across the entire Davinci monorepo - add `pnpm-workspace.yaml`, `.npmrc`, and `packageManager` field for corepack support - convert Yarn `resolutions` to `pnpm.overrides` in root `package.json` - update lerna `npmClient` from `yarn` to `pnpm` - replace `yarn` with `pnpm` in root scripts (postinstall, test, test:unit:update) **HOW to update:** - install pnpm (`corepack enable` or `npm install -g pnpm@10.6.1`) - replace `yarn install` with `pnpm install` in local workflows - replace `yarn