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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update all dependencies #31

Merged
merged 1 commit into from
Nov 7, 2023
Merged

chore(deps): update all dependencies #31

merged 1 commit into from
Nov 7, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 30, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@intlify/unplugin-vue-i18n (source) 1.2.0 -> 1.5.0 age adoption passing confidence
@playwright/test (source) 1.36.1 -> 1.39.0 age adoption passing confidence
@rushstack/eslint-patch (source) 1.3.2 -> 1.5.1 age adoption passing confidence
@testing-library/jest-dom 6.0.0 -> 6.1.4 age adoption passing confidence
@testing-library/user-event 14.4.3 -> 14.5.1 age adoption passing confidence
@testing-library/vue ^7.0.0 -> ^8.0.0 age adoption passing confidence
@types/node (source) 20.4.2 -> 20.8.10 age adoption passing confidence
@​types/testing-library__jest-dom 5.14.8 -> 5.14.9 age adoption passing confidence
@vitejs/plugin-vue (source) 4.2.3 -> 4.4.0 age adoption passing confidence
@vitest/coverage-v8 (source) 0.34.0 -> 0.34.6 age adoption passing confidence
autoprefixer 10.4.14 -> 10.4.16 age adoption passing confidence
axios (source) 1.4.0 -> 1.6.0 age adoption passing confidence
eslint (source) 8.44.0 -> 8.53.0 age adoption passing confidence
eslint-plugin-testing-library 6.0.0 -> 6.1.0 age adoption passing confidence
eslint-plugin-vue (source) 9.15.1 -> 9.18.1 age adoption passing confidence
lint-staged 15.0.1 -> 15.0.2 age adoption passing confidence
msw (source) 2.0.1 -> 2.0.3 age adoption passing confidence
pinia 2.1.4 -> 2.1.7 age adoption passing confidence
pinia-plugin-persistedstate (source) 3.1.0 -> 3.2.0 age adoption passing confidence
postcss-nesting (source) 12.0.0 -> 12.0.1 age adoption passing confidence
prettier (source) 3.0.0 -> 3.0.3 age adoption passing confidence
tailwindcss (source) 3.3.2 -> 3.3.5 age adoption passing confidence
typescript (source) 5.0.2 -> 5.2.2 age adoption passing confidence
unplugin-vue-components 0.25.1 -> 0.25.2 age adoption passing confidence
vite (source) 4.4.0 -> 4.5.0 age adoption passing confidence
vitest 0.34.0 -> 0.34.6 age adoption passing confidence
vue (source) 3.3.4 -> 3.3.8 age adoption passing confidence
vue-i18n (source) 9.6.1 -> 9.6.5 age adoption passing confidence
vue-router 4.2.4 -> 4.2.5 age adoption passing confidence
vue-tsc 1.8.3 -> 1.8.22 age adoption passing confidence

Release Notes

intlify/bundle-tools (@​intlify/unplugin-vue-i18n)

v1.5.0

Compare Source

⭐ Features
Committers: 1

v1.4.0

Compare Source

⭐ Features
Committers: 1

v1.3.0

Compare Source

⭐ Features
Committers: 1
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

v1.37.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/26496 - [REGRESSION] webServer stdout is always getting printedhttps://github.com/microsoft/playwright/issues/264922 - [REGRESSION] test.only with project dependency is not working

Browser Versions

  • Chromium 116.0.5845.82
  • Mozilla Firefox 115.0
  • WebKit 17.0

This version was also tested against the following stable channels:

  • Google Chrome 115
  • Microsoft Edge 115

v1.37.0

Compare Source

Watch the overview: Playwright 1.36 & 1.37

✨ New tool to merge reports

If you run tests on multiple shards, you can now merge all reports in a single HTML report (or any other report)
using the new merge-reports CLI tool.

Using merge-reports tool requires the following steps:

  1. Adding a new "blob" reporter to the config when running on CI:

    export default defineConfig({
  testDir: './tests',
  reporter: process.env.CI ? 'blob' : 'html',
});

    The "blob" reporter will produce ".zip" files that contain all the information
    about the test run.

  2. Copying all "blob" reports in a single shared location and running npx playwright merge-reports:

    npx playwright merge-reports --reporter html ./all-blob-reports

Read more in our documentation.

📚 Debian 12 Bookworm Support

Playwright now supports Debian 12 Bookworm on both x86_64 and arm64 for Chromium, Firefox and WebKit.
Let us know if you encounter any issues!

Linux support looks like this:

Ubuntu 20.04 Ubuntu 22.04 Debian 11 Debian 12
Chromium ✅ ✅ ✅ ✅
WebKit ✅ ✅ ✅ ✅
Firefox ✅ ✅ ✅ ✅

🌈 UI Mode Updates

  • UI Mode now respects project dependencies. You can control which dependencies to respect by checking/unchecking them in a projects list.
  • Console logs from the test are now displayed in the Console tab.

Browser Versions

  • Chromium 116.0.5845.82
  • Mozilla Firefox 115.0
  • WebKit 17.0

This version was also tested against the following stable channels:

  • Google Chrome 115
  • Microsoft Edge 115

v1.36.2: 1.36.2

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/24316 - [REGRESSION] Character classes are not working in globs in 1.36

Browser Versions
  • Chromium 115.0.5790.75
  • Mozilla Firefox 115.0
  • WebKit 17.0

This version was also tested against the following stable channels:

  • Google Chrome 114
  • Microsoft Edge 114
microsoft/rushstack (@​rushstack/eslint-patch)

v1.5.1

Compare Source

testing-library/jest-dom (@​testing-library/jest-dom)

v6.1.4

Compare Source

Bug Fixes
  • upgrade @adobe/css-tools to 4.3.1 to address vulnerability (#​532) (44f1eab)

v6.1.3

Compare Source

Bug Fixes

v6.1.2

Compare Source

Bug Fixes

v6.1.1

Compare Source

Bug Fixes

v6.1.0

Compare Source

Features

v6.0.1

Compare Source

Bug Fixes
  • matchers type is making the global expect unsafe (#​513) (bdb34f1)
testing-library/user-event (@​testing-library/user-event)

v14.5.1

Compare Source

Bug Fixes

v14.5.0

Compare Source

Bug Fixes
Features
  • types: Add additional type exports for UserEvent & Options (#​1112) (da00e8d)
testing-library/vue-testing-library (@​testing-library/vue)

v8.0.0

Compare Source

bug
  • Fix issue on Vite env not cleaning up after test (#​297) (88fb8cd)
BREAKING CHANGES
  • This PR change default behavior for Vitest users. This major should yield no effect to other test frameworks.

Throw error when running vitest with no afterEach global and no VTL_SKIP_AUTO_CLEANUP flag is set.

vitejs/vite-plugin-vue (@​vitejs/plugin-vue)

v4.4.0

v4.3.4

Compare Source

v4.3.3

Compare Source

v4.3.2

Compare Source

v4.3.1

Compare Source

  • fix: revert "fix(plugin-vue): distinguish HMR and transform descriptor (#​227)" (0c28448), closes #​227

v4.3.0

Compare Source

vitest-dev/vitest (@​vitest/coverage-v8)

v0.34.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.34.4

Compare Source

   🐞 Bug Fixes

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.

@renovate renovate bot force-pushed the renovate/all branch 6 times, most recently from 4154470 to c6b7318 Compare November 4, 2023 04:54
@tzuyi0817 tzuyi0817 merged commit a4dc91e into main Nov 7, 2023
@tzuyi0817 tzuyi0817 deleted the renovate/all branch November 7, 2023 01:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@tzuyi0817