Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Bump stable packages - abandoned #201

Closed
wants to merge 4 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 22, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@croct/json 2.0.1 -> 2.1.0 age adoption passing confidence
@playwright/test (source) 1.37.1 -> 1.39.0 age adoption passing confidence
@rollup/plugin-commonjs (source) 25.0.4 -> 25.0.7 age adoption passing confidence
@rollup/plugin-node-resolve (source) 15.2.0 -> 15.2.3 age adoption passing confidence
@rollup/plugin-replace (source) 5.0.2 -> 5.0.4 age adoption passing confidence
@rollup/plugin-typescript (source) 11.1.2 -> 11.1.5 age adoption passing confidence
@types/jest (source) 29.5.3 -> 29.5.6 age adoption passing confidence
jest (source) 29.6.2 -> 29.7.0 age adoption passing confidence
jest-environment-jsdom 29.6.2 -> 29.7.0 age adoption passing confidence
parcel 2.9.3 -> 2.10.0 age adoption passing confidence
rollup (source) 3.28.0 -> 3.29.4 age adoption passing confidence
typescript (source) 5.1.6 -> 5.2.2 age adoption passing confidence

Release Notes

croct-tech/json-js (@​croct/json)

v2.1.0

Compare Source

What's Changed

🚀 Features

  • Add re-exports of JSON methods with proper types (#​56), thanks Fryuni!

🔧 Enhancements

  • Rename typed methods and relax stringify input (#​57), thanks Fryuni!

🚧 Maintenance

🎉 Thanks to all contributors helping with this release:
@​Fryuni, @​renovate and @​renovate[bot]

microsoft/playwright (@​playwright/test)

v1.39.0

Compare Source

Add custom matchers to your expect

You can extend Playwright assertions by providing custom matchers. These matchers will be available on the expect object.

import { expect as baseExpect } from '@​playwright/test';
export const expect = baseExpect.extend({
  async toHaveAmount(locator: Locator, expected: number, options?: { timeout?: number }) {
    // ... see documentation for how to write matchers.
  },
});

test('pass', async ({ page }) => {
  await expect(page.getByTestId('cart')).toHaveAmount(5);
});

See the documentation for a full example.

Merge test fixtures

You can now merge test fixtures from multiple files or modules:

import { mergeTests } from '@​playwright/test';
import { test as dbTest } from 'database-test-utils';
import { test as a11yTest } from 'a11y-test-utils';

export const test = mergeTests(dbTest, a11yTest);
import { test } from './fixtures';

test('passes', async ({ database, page, a11y }) => {
  // use database and a11y fixtures.
});

Merge custom expect matchers

You can now merge custom expect matchers from multiple files or modules:

import { mergeTests, mergeExpects } from '@​playwright/test';
import { test as dbTest, expect as dbExpect } from 'database-test-utils';
import { test as a11yTest, expect as a11yExpect } from 'a11y-test-utils';

export const test = mergeTests(dbTest, a11yTest);
export const expect = mergeExpects(dbExpect, a11yExpect);
import { test, expect } from './fixtures';

test('passes', async ({ page, database }) => {
  await expect(database).toHaveDatabaseUser('admin');
  await expect(page).toPassA11yAudit();
});

Hide implementation details: box test steps

You can mark a test.step() as "boxed" so that errors inside it point to the step call site.

async function login(page) {
  await test.step('login', async () => {
    // ...
  }, { box: true });  // Note the "box" option here.
}
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
  ... error details omitted ...

  14 |   await page.goto('https://github.com/login');
> 15 |   await login(page);
     |         ^
  16 | });

See test.step() documentation for a full example.

New APIs

Browser Versions

  • Chromium 119.0.6045.9
  • Mozilla Firefox 118.0.1
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 118
  • Microsoft Edge 118

v1.38.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/27071 - expect(value).toMatchSnapshot() deprecation announcement on V1.38
https://github.com/microsoft/playwright/issues/27072 - [BUG] PWT trace viewer fails to load trace and throws TypeErrorhttps://github.com/microsoft/playwright/issues/270733 - [BUG] RangeError: Invalid time valuhttps://github.com/microsoft/playwright/issues/2708787 - [REGRESSION]: npx playwright test --list prints all tests twihttps://github.com/microsoft/playwright/issues/27113113 - [REGRESSION]: No longer able to extend PlaywrightTest.Matchers type for locators and pahttps://github.com/microsoft/playwright/issues/271447144 - [BUG]can not display thttps://github.com/microsoft/playwright/issues/2716327163 - [REGRESSION] Single Quote Wrongly Escaped by Locator When Using Unicodehttps://github.com/microsoft/playwright/issues/27181/27181 - [BUG] evaluate serializing fails at 1.38

Browser Versions
  • Chromium 117.0.5938.62
  • Mozilla Firefox 117.0
  • WebKit 17.0

This version was also tested against the following stable channels:

  • Google Chrome 116
  • Microsoft Edge 116

v1.38.0

Compare Source

UI Mode Updates

Playwright UI Mode

  1. Zoom into time range.
  2. Network panel redesign.

New APIs

  • [browserContext.on('weberror')][browserContext.on('weberror')]
  • [locator.pressSequentially()][locator.pressSequentially()]
  • The [reporter.onEnd()][reporter.onEnd()] now reports startTime and total run duration.

Deprecations

  • The following methods were deprecated: [page.type()][page.type()], [frame.type()][frame.type()], [locator.type()][locator.type()] and [elementHandle.type()][elementHandle.type()].
    Please use [locator.fill()][locator.fill()] instead which is much faster. Use [locator.pressSequentially()][locator.pressSequentially()] only if there is a
    special keyboard handling on the page, and you need to press keys one-by-one.

Breaking Changes: Playwright no longer downloads browsers automatically

[!NOTE]
If you are using @playwright/test package, this change does not affect you.

Playwright recommends to use @playwright/test package and download browsers via npx playwright install command. If you are following this recommendation, nothing has changed for you.

However, up to v1.38, installing the playwright package instead of @playwright/test did automatically download browsers. This is no longer the case, and we recommend to explicitly download browsers via npx playwright install command.

v1.37 and earlier

playwright package was downloading browsers during npm install, while @playwright/test was not.

v1.38 and later

playwright and @playwright/test packages do not download browsers during npm install.

Recommended migration

Run npx playwright install to download browsers after npm install. For example, in your CI configuration:

- run: npm ci
- run: npx playwright install --with-deps

Alternative migration option - not recommended

Add @playwright/browser-chromium, @playwright/browser-firefox and @playwright/browser-webkit as a dependency. These packages download respective browsers during npm install. Make sure you keep the version of all playwright packages in sync:

// package.json
{
  "devDependencies": {
    "playwright": "1.38.0",
    "@​playwright/browser-chromium": "1.38.0",
    "@​playwright/browser-firefox": "1.38.0",
    "@​playwright/browser-webkit": "1.38.0"
  }
}
Browser Versions
  • Chromium 117.0.5938.62
  • Mozilla Firefox 117.0
  • WebKit 17.0

This version was also tested against the following stable channels:

  • Google Chrome 116
  • Microsoft Edge 116
rollup/plugins (@​rollup/plugin-commonjs)

v25.0.7

Compare Source

2023-10-15

Bugfixes
  • fix: bump magic-string version #​1596

v25.0.6

Compare Source

2023-10-15

Bugfixes
  • fix: Keep the shebang at the top of the file content #​1610

v25.0.5

Compare Source

2023-10-05

Bugfixes
  • fix: ensure rollup 4 compatibility #​1595
rollup/plugins (@​rollup/plugin-node-resolve)

v15.2.3

Compare Source

2023-10-08

Bugfixes
  • fix: modulePaths default is not set #​1534

v15.2.2

Compare Source

2023-10-05

Bugfixes
  • fix: ensure rollup 4 compatibility #​1595

v15.2.1

Compare Source

2023-08-22

Bugfixes
  • fix: Implement package exports / imports resolution algorithm according to Node documentation #​1549
rollup/plugins (@​rollup/plugin-replace)

v5.0.4

Compare Source

2023-10-15

Bugfixes
  • fix: bump magic-string version #​1596

v5.0.3

Compare Source

2023-10-05

Bugfixes
  • fix: ensure rollup 4 compatibility #​1595
rollup/plugins (@​rollup/plugin-typescript)

v11.1.5

Compare Source

2023-10-05

Bugfixes
  • fix: ensure rollup 4 compatibility #​1595

v11.1.4

Compare Source

2023-09-25

Bugfixes
  • fix: fix sourcemap sourcecontent referencing non-existent files #​1571

v11.1.3

Compare Source

2023-08-26

Bugfixes
  • fix: emit declaration files for type-only source files that are not explicitly included #​1555
jestjs/jest (jest)

v29.7.0

Compare Source

Features
  • [create-jest] Add npm init / yarn create initialiser for Jest projects (#​14465)
  • [jest-validate] Allow deprecation warnings for unknown options (#​14499)
Fixes
  • [jest-resolver] Replace unmatched capture groups in moduleNameMapper with empty string instead of undefined (#​14507)
  • [jest-snapshot] Allow for strings as well as template literals in inline snapshots (#​14465)
  • [@jest/test-sequencer] Calculate test runtime if perStats.duration is missing (#​14473)
Performance
  • [@jest/create-cache-key-function] Cache access of NODE_ENV and BABEL_ENV (#​14455)
Chore & Maintenance
  • [jest-cli] Move internal config initialisation logic to the create-jest package (#​14465)

v29.6.4

Compare Source

Fixes
  • [jest-core] Fix typo in scheduleAndRun performance marker (#​14434)
  • [jest-environment-node] Make sure atob and btoa are writeable in Node 20 (#​14446)
  • [jest-worker] Additional error wrapper for parentPort.postMessage to fix unhandled DataCloneError. (#​14437)

v29.6.3

Compare Source

Fixes
  • [expect, @​jest/expect-utils] ObjectContaining support sumbol as key (#​14414)
  • [expect] Remove @types/node from dependencies (#​14385)
  • [jest-core] Use workers in watch mode by default to avoid crashes (#​14059 & #​14085).
  • [jest-reporters] Update istanbul-lib-instrument dependency to v6. (#​14401)
  • [jest-mock] Revert #​13692 as it was a breaking change (#​14429)
  • [jest-mock] Revert #​13866 as it was a breaking change (#​14429)
  • [jest-mock] Revert #​13867 as it was a breaking change (#​14429)
  • [@jest/reporters] Marks Reporter's hooks as optional (#​14433)
  • [jest-runtime] Fix dynamic ESM import module bug when loaded module through jest.isolateModulesAsync (#​14397)
Chore & Maintenance
  • [jest-changed-files, jest-circus, jest-console, @​jest/core, @​jest/runtime, @​jest/transform] Use invariant and notEmpty from jest-util rather than own internal (#​14366)
parcel-bundler/parcel (parcel)

v2.10.0

Compare Source

Added
  • Core

    • Add support for include and exclude globs for --lazy mode – Details, Details
    • Merge all native Rust modules into one package – Details
    • Add async resolver and JS transformer functions using rayon – Details
    • Support "register" tools in module loader (e.g. @babel/register, esbuild-register, ts-node) – Details
    • Limit default number of JS workers to 4 to improve memory usage/performance – Details
  • Bundler

    • Optimize bundler performance – Details
    • Add disableSharedBundles config option – Details
  • Resolver

  • JavaScript

    • Add import helper to decrease ESM loader runtime footprint – Details
    • Support parallel bundle imports in libraries – Details
    • Only include globalThis polyfill for old browsers – Details
    • Updated parcelRequire.register to be minifiable – Details
  • CSS

    • Add include and exclude globs for CSS modules – Details
  • WASM

    • Add WASM packager with source map support – Details
  • XML

    • Transform xml-stylesheet processing instructions – Details
  • Web Extensions

    • Add support for Chrome Extension manifest V3 side_panel property – Details
    • Improve HMR for web extensions – Details
  • Web Manifest

    • Add support for icons in file_handlers – Details
Fixed
  • Core

    • Query glibc version only once to speed up JSTransformer on Linux – Details
    • Refresh cache before writing contents to bundle – Details
    • Fix --lazy mode bugs – Details
    • Ignore no-opt command line option – Details
    • Bump lmdb – Details
    • Don't hide error when diagnostic is malformed – Details
    • Don't autoinstall local files in package manager – Details
    • Fix bug with cache and glob entries – Details
  • JavaScript

    • Migrate to swc_core – Details
    • Move ESM loader runtime to absolute URLs – Details
    • Fix duplicate asset references – Details
    • Bump swc – Details, Details, Details
    • Fix shorthand identifier import usage – Details
    • Ensure nested member expressions are marked used in dev mode – Details
    • Set ascii_only for swc emit – Details
    • Add tests for non-identifier symbol names – Details
  • Bundler

    • Exclude inline assests from parallel request limit – Details
    • Fix unexpected undefined when creating shared bundles – Details
  • Images

    • Bump oxipng from 6.0.0 -> 8.0.0 – Details
  • Sass

    • Fix sass import edge case – Details
  • Dev Server

    • Fix index page loading in dev server when bundle type isn't html – Details
Unstable
  • Core

    • Expose unstable_transform and unstable_resolve APIs – Details
  • Bundler

    • Add unstable manual shared bundles config – Details
  • JavaScript

    • Experimental inline / deferred requires optimiser – Details
    • Add constants inlining optimization – Details
    • Add unstable async bundle runtime to the JS Packager – Details
rollup/rollup (rollup)

v3.29.4

Compare Source

2023-09-28

Bug Fixes
  • Fix static analysis when an exported function uses callbacks (#​5158)
Pull Requests

v3.29.3

Compare Source

2023-09-24

Bug Fixes
  • Fix a bug where code was wrongly tree-shaken after mutating function parameters (#​5153)
Pull Requests

v3.29.2

Compare Source

2023-09-15

Bug Fixes
  • Export TreeshakingPreset type (#​5131)
Pull Requests

v3.29.1

Compare Source

2023-09-10

Bug Fixes
  • Fix time measurement of plugin hooks in watch mode (#​5114)
  • Ensure accessing document.currentScript in import.meta.url returns correct results (#​5118)
Pull Requests

v3.29.0

Compare Source

2023-09-06

Features
  • Add output.sourcemapFileNames option (#​5105)
  • Add generic type parameter for api to Plugin type (#​5112)
Bug Fixes
  • Ensure mutations of CustomEvent details are tracked (#​5123)
Pull Requests

v3.28.1

Compare Source

2023-08-22

Bug Fixes
  • Ensure external files with relative import paths outside the target are rendered correctly (#​5099)
Pull Requests
Microsoft/TypeScript (typescript)

v5.2.2: TypeScript 5.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:


Configuration

📅 Schedule: Branch creation - "before 4am every weekday" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.

@renovate renovate bot added the maintenance Housekeeping label Aug 22, 2023
@renovate renovate bot enabled auto-merge (rebase) August 22, 2023 01:35
renovate-approve[bot]
renovate-approve bot previously approved these changes Aug 22, 2023
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Aug 22, 2023
@renovate renovate bot changed the title Update Bump stable packages to v29.6.3 Update Bump stable packages Aug 22, 2023
@renovate renovate bot force-pushed the renovate/bump-stable-packages branch from 0ec6ba6 to 6918886 Compare August 22, 2023 07:23
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Aug 22, 2023
renovate-approve[bot]
renovate-approve bot previously approved these changes Aug 22, 2023
@renovate renovate bot force-pushed the renovate/bump-stable-packages branch from 6918886 to 27f31f0 Compare August 22, 2023 22:57
renovate-approve[bot]
renovate-approve bot previously approved these changes Aug 22, 2023
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Aug 22, 2023
@renovate renovate bot force-pushed the renovate/bump-stable-packages branch from 27f31f0 to 32283dd Compare August 24, 2023 14:51
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Aug 24, 2023
renovate-approve[bot]
renovate-approve bot previously approved these changes Aug 24, 2023
@renovate renovate bot force-pushed the renovate/bump-stable-packages branch from 32283dd to ad02c06 Compare August 24, 2023 17:10
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Aug 24, 2023
renovate-approve[bot]
renovate-approve bot previously approved these changes Aug 24, 2023
@renovate renovate bot force-pushed the renovate/bump-stable-packages branch from ad02c06 to 45a61ed Compare August 26, 2023 20:15
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Aug 26, 2023
renovate-approve[bot]
renovate-approve bot previously approved these changes Aug 26, 2023
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Oct 11, 2023
@renovate renovate bot force-pushed the renovate/bump-stable-packages branch from 07efb41 to 42a1fc6 Compare October 12, 2023 01:30
renovate-approve[bot]
renovate-approve bot previously approved these changes Oct 12, 2023
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Oct 12, 2023
@renovate renovate bot force-pushed the renovate/bump-stable-packages branch from 42a1fc6 to 9b26270 Compare October 15, 2023 16:46
renovate-approve[bot]
renovate-approve bot previously approved these changes Oct 15, 2023
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Oct 15, 2023
@renovate renovate bot force-pushed the renovate/bump-stable-packages branch from 9b26270 to 171d821 Compare October 18, 2023 08:18
renovate-approve-2[bot]
renovate-approve-2 bot previously approved these changes Oct 18, 2023
renovate-approve[bot]
renovate-approve bot previously approved these changes Oct 18, 2023
Comment on lines +80 to +81
jest.restoreAllMocks();
jest.clearAllMocks();
Copy link
Member

@denis-rossati denis-rossati Oct 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I choose to use restore over reset because the reset replaces the mock with an empty function that return undefined, leading some tests to errors since we are mocking the window.removeEventListener and window.addEventListener, on the other hand, the restore will restore the original function, and since we are spying the window again in the beforeEach, I see no problem.

The clearAllMocks is here because the restoreMock restore only jest.spyOn mocks, so the clear will deal with jest.fn() mocks

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Relevant docs.

clearAllMocks clears the call history for every mock. Good.

resetAllMocks calls clearAllMocks plus replaces the mock implementation with a function returning undefined. If that is the problematic behavior, we should replace the call with just clearAllMocks.

restoreAllMocks removes the mock. After this call, all mocks that can be restored are no longer mocked. This might open up potential flaky tests, regressions, and false negatives since we no longer mock the situation we want to test. If there is a test after this call validating that internal errors are not propagated, for example, it would become a non-error scenario, and the code would no longer be tested.

@renovate
Copy link
Contributor Author

renovate bot commented Oct 18, 2023

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.

@Fryuni Fryuni disabled auto-merge November 13, 2023 10:59
Comment on lines +80 to +81
jest.restoreAllMocks();
jest.clearAllMocks();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Relevant docs.

clearAllMocks clears the call history for every mock. Good.

resetAllMocks calls clearAllMocks plus replaces the mock implementation with a function returning undefined. If that is the problematic behavior, we should replace the call with just clearAllMocks.

restoreAllMocks removes the mock. After this call, all mocks that can be restored are no longer mocked. This might open up potential flaky tests, regressions, and false negatives since we no longer mock the situation we want to test. If there is a test after this call validating that internal errors are not propagated, for example, it would become a non-error scenario, and the code would no longer be tested.

@renovate renovate bot changed the title Update Bump stable packages Update Bump stable packages - abandoned Nov 20, 2023
Copy link
Contributor Author

renovate bot commented Nov 20, 2023

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

@Fryuni Fryuni closed this Nov 20, 2023
@Fryuni Fryuni deleted the renovate/bump-stable-packages branch November 20, 2023 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Housekeeping
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants