This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @antfu/eslint-config | 0.20.6 -> 0.21.1 | ||||
| autoprefixer | 10.4.4 -> 10.4.5 | ||||
| cypress | 9.5.4 -> 9.6.0 | ||||
| eslint (source) | 8.13.0 -> 8.14.0 | ||||
| pnpm (source) | 6.32.9 -> 6.32.10 | ||||
| vitest | 0.9.4 -> 0.10.0 | ||||
| vue-tsc | 0.34.9 -> 0.34.10 |
Release Notes
cypress-io/cypress
v9.6.0
Released 4/25/2022
Features:
- Now you can easily test multi-domain workflows by using the experimental
cy.origin()command. This feature allows you to test across different origins or domains within a single test. This experiment was designed to work side-by-side with thecy.session()experimental feature. You can turn on use of this command by setting theexperimentalSessionAndOriginconfiguration option totrue. For more details, read our blog post. Addressed #17336 and #944.- Added a new configuration option called
experimentalSessionAndOrigin. This option enables support forcy.session()andcy.origin(). - The
experimentalSessionSupportconfiguration option has been removed and replaced by theexperimentalSessionAndOriginconfiguration option. Please update your configuration to use the newexperimentalSessionAndOriginoption to continue to opt-in to this experimental feature. - When
experimentalSessionAndOriginis enabled, cross-origin requests will no longer immediately fail, but instead, time out based on thepageLoadTimeoutconfiguration. This allows the request to be appropriately handled by thecy.origin()command. - When
experimentalSessionAndOriginis enabled, Cypress will no longer wait on page loads between hooks before moving on to the next test.
- Added a new configuration option called
Bugfixes:
- Fixed an issue with Firefox 98+ where the Enter keystroke was not being sent
to an input element when using
.type('{enter}'). Fixed #21033. - We now verify if an interruption while running tests was signaled by the user or if it came from an error in a plugin before showing the error message. Fixed #21010.
- Improved the error message observed on Windows platforms when unzipping the Cypress binary and the max file length is exceeded. Fixed in #21047.
- Updated the
Cypress.Commands.add()TypeScript types to better reflect the attributes of the.add()utility and the JQuery element, a possible previous subject type. #20376.
Dependency Updates:
- Upgraded
electrondependency from15.3.5to15.5.1to consume fixes related to improve performance on macOS Big Sur and later. Addressed #21068.
eslint/eslint
v8.14.0
Features
Bug Fixes
35fa1ddfix: allow project paths to have URL-encoded characters (#15795) (Milos Djermanovic)413f1d5fix: updateastUtils.isDirectiveCommentwithglobalsandexported(#15775) (Milos Djermanovic)
Build Related
Chores
pnpm/pnpm
v6.32.10
Patch Changes
- It should be possible to use a chain of local file dependencies #4611.
- Filtering by directory should work with directories that have unicode chars in the name #4595.
Full Changelog: https://github.com/pnpm/pnpm/compare/v6.32.9...v6.32.10
vitest-dev/vitest
v0.10.0
Breaking Changes
From Vitest v0.10.0, the callback style of declaring tests is deprecated. You can rewrite them to use async/await functions, or use Promise to mimic the callback style.
- it('should work', (done) => {
+ it('should work', () => new Promise(done => {
// ...
done()
- })
+ }))Features
beforeAll / beforeEach cleanup callback
beforeAll / beforeEach now accepts an optional cleanup function as the return value (equivalent to afterAll / afterEach).
import { beforeAll } from 'vitest'
beforeEach(async () => {
// called once before each test run
await startMocking()
// clean up function, called once after each test run
return async () => {
await stopMocking()
}
})Learn more at:
Test Context
Inspired by Playwright Fixtures, Vitest's test context allows you to define utils, states, and fixtures that can be used in your tests.
import { beforeEach, it } from 'vitest'
beforeEach((context) => {
// extend context
context.foo = 'bar'
})
it('should work', ({ foo }) => {
console.log(foo) // 'bar'
})Learn more at Test Context
Concurrent Snapshot
Due to the limitation of JavaScript, timing based Singleton pattern will cause conflicts when running multiple async functions in concurrent. Previously reported as #551. Thanks to the newly introduced Test Context, we can now provide a test specific expect instance to avoid conflicts. To use it, you can destructure the expect from each test context instead of the global one.
test.concurrent('test 1', async ({ expect }) => {
expect(foo).toMatchSnapshot()
})
test.concurrent('test 2', async ({ expect }) => {
expect(foo).toMatchSnapshot()
})Reporter from file / package
Now you can pass a path to file, or a package name to the reporters options to use custom reporter. Thanks to @ericjgagnon (#1136) (f2bceb2)
Bug Fixes
johnsoncodehk/volar
v0.34.10
- fix: template bindings error incomplete (#1205)
- fix: avoid auto-import added on same line as
<script>(#916) - fix: embedded html interpolations syntax highlight not working in markdown
- fix: inlay hints not working in template
- fix: preview broken on nuxt3 rc (#1225)
- fix: cannot use import equals in script setup (#1223)
- fix: directives syntax highlight display incorrect in html comment inside svg tag (#1206)
Configuration
📅 Schedule: 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, click this checkbox.
This PR has been generated by WhiteSource Renovate. View repository job log here.