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

chore(deps): update all non-major dependencies #15

Merged
merged 1 commit into from
Sep 6, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 25, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
c8 ^7.11.2 -> ^7.11.3 age adoption passing confidence
pnpm (source) 6.32.10 -> 6.32.24 age adoption passing confidence
vitest ^0.9.4 -> ^0.16.0 age adoption passing confidence

Release Notes

bcoe/c8

v7.11.3

Compare Source

pnpm/pnpm

v6.32.24

Compare Source

Patch Changes
  • Don't crash when pnpm update --interactive is cancelled with Ctrl+c.

  • The use-node-version setting should work with prerelease Node.js versions. For instance:

    use-node-version=18.0.0-rc.3
    

v6.32.23

Compare Source

Patch Changes
  • Packages that should be built are always cloned or copied from the store. This is required to prevent the postinstall scripts from modifying the original source files of the package #​4898.

v6.32.22

Compare Source

Patch Changes
  • Don't fail when the cafile setting is specified #​4877. This fixes a regression introduced in pnpm v6.32.21.
  • Add better hints to the peer dependency issue errors.

v6.32.21

Compare Source

Patch Changes
  • Report only the first occurence of a deprecated package.

v6.32.20

Compare Source

Patch Changes
  • Suggest to update using Corepack when pnpm was installed via Corepack.
  • It should be possible to install a git-hosted package that has no package.json file #​4822.
  • When the same package is found several times in the dependency graph, correctly autoinstall its missing peer dependencies at all times #​4820.

v6.32.19

Compare Source

Patch Changes
  • Improve the performance of the build sequence calculation step #​4815.
  • Correctly detect repeated dependency sequence during resolution #​4813.

v6.32.18

Compare Source

Patch Changes
  • Don't fail on projects with linked dependencies, when auto-install-peers is set to true #​4796.
  • NODE_ENV=production pnpm install --dev should only install dev deps #​4745.

Full Changelog: pnpm/pnpm@v6.32.17...v6.32.18

v6.32.17

Compare Source

Patch Changes
  • Correctly detect the active Node.js version, when the pnpm CLI is bundled to an executable #​4203.

v6.32.16

Compare Source

Patch Changes
  • When auto-install-peers is set to true, automatically install missing peer dependencies without writing them to package.json as dependencies. This makes pnpm handle peer dependencies the same way as npm v7 #​4776.

v6.32.15

Compare Source

Patch Changes
  • Don't fail to create the command shim files if the target directory doesn't exist.
  • pnpm setup should not fail on Windows if PNPM_HOME is not yet in the system registry #​4757
  • pnpm dlx shouldn't modify the lockfile in the current working directory #​4743.

v6.32.14

Compare Source

Patch Changes
  • Sanitize the directory names created inside node_modules/.pnpm and inside the global store #​4716
  • Resolve commits from GitHub via https #​4734.

Full Changelog: pnpm/pnpm@v6.32.13...v6.32.14

v6.32.13

Compare Source

Patch Changes
  • pnpm setup should update the config of the current shell, not the preferred shell.
  • pnpm dlx should work with git-hosted packages. For example: pnpm dlx gengjiawen/envinfo #​4714.
  • pnpm setup should not override the PNPM_HOME env variable on Windows, unless --force is used.
  • All arguments after pnpm create <pkg> should be passed to the executed create app package. So pnpm create next-app --typescript should work`.
  • pnpm run --stream should prefix the output with directory #​4702

Full Changelog: pnpm/pnpm@v6.32.12...v6.32.13

v6.32.12

Compare Source

Patch Changes
  • Use Yarn's compatibility database to patch broken packages in the ecosystem with package extensions.
  • pnpm dlx should work when the bin name of the executed package isn't the same as the package name #​4672.
  • pnpm prune works in a workspace #​4647.
  • pnpm prune does not remove hoisted dependencies.
  • pnpm dlx should print messages about installation to stderr #​1698.

v6.32.11

Compare Source

Patch Changes
  • pnpm publish should work correctly in a workspace, when the latest npm CLI is installed #​4348.
  • Installation shouldn't fail when a package from node_modules is moved to the node_modules/.ignored subfolder and a package with that name is already present in `node_modules/.ignored' #​4626.

Full Changelog: pnpm/pnpm@v6.32.10...v6.32.11

vitest-dev/vitest

v0.16.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.15.2

Compare Source

   🐞 Bug Fixes
  • Allow redefining global expect, closes #1496
  • Calculate label of graph node #1431
  • Snapshots are now updating #1503
  • Return types for vi.mocked are now equal to MaybeMocked #1511
  • Don't mark skipped snapshots as obsolete #1505
  • Correctly generate inline snapshots inside js files #1510
  • Respect transformMode when resolving id #1506
   ❤️ Contributors

   Thanks to @​antfu | @​nieyuyao | @​RedJanvier | @​renovate[bot] | @​sheremet-va

    View changes on GitHub

v0.15.1

Compare Source

   🐞 Bug Fixes
  • Reliably process css with css option 22fed1b8
   ❤️ Contributors

   Thanks to @​sheremet-va | @​stormwarning

    View changes on GitHub

v0.15.0

Compare Source

   🚀 Features
  • Bind expect state to context #1468
  • Introduce VITEST_POOL_ID #1473
  • Add maxConcurrency option, 5 by default #1483
  • Add --shard command #1477
  • Add css config option, don't process CSS by default #1467
   🐞 Bug Fixes
  • Null inside test.each is not turned into an empty array #1462
  • Add @​types/node to dependencies #1474
  • Parent is defined on global, closes #1489
  • web-worker:
    • Ensure event listener functions are bound correctly #1487
    View changes on GitHub

v0.14.2

Compare Source

Bug Fixes
Features

v0.14.1

Compare Source

Bug Fixes

v0.14.0

Compare Source

Breaking Changes

  • vite-node: use .mjs for esm build (692ad34)
  • remove "type": "module" from vitest/package.json (#​1411) (b4a9b0b), closes #​325
  • vite-node: respect ssr field, allow inlining everything (#​1434) (fd57b0e)
  • improve watcher performance, add forceRerunTriggers option, watchIgnore is renamed to watchExclude and now accepts only glob patterns (#​1424) (3f5ff5b)
Bug Fixes

v0.13.1

Compare Source

Bug Fixes
Features

v0.13.0

Compare Source

Features

v0.12.10

Compare Source

Bug Fixes
Features

v0.12.9

Compare Source

Bug Fixes

v0.12.8

Compare Source

Bug Fixes

v0.12.7

Compare Source

Bug Fixes
Features

v0.12.6

Compare Source

Bug Fixes

v0.12.5

Compare Source

Bug Fixes
Features
  • vite-node: include debug (ed3374f)

v0.12.4

Compare Source

Bug Fixes
  • snapshot: only add indent when the line is not empty (6a5dfe8)
Features

v0.12.3

Compare Source

Bug Fixes
  • try disable atomics for workers (154db71)

v0.12.2

Compare Source

Bug Fixes
Features
  • support custom env in config (4701e0b)

v0.12.1

Compare Source

Bug Fixes
  • fix require reference (5da8b00)
  • console: ignore empty stdout/stderr (d3fb532)
  • clear mock from callstack, if mocked with factory (#​1276) (7459ff8)
  • don't show __vite_ssr prefix on imported variables (#​1272) (a2f17b0)
Features

v0.12.0

Compare Source

Bug Fixes
  • calling global functions in happy-dom, refactor sharing global state (#​1262) (555aba6)
Features

v0.11.0

Compare Source

Bug Fixes
Features

v0.10.5

Compare Source

Bug Fixes
Features
  • remove shebang when executing the code via vite-node (#​1224) (5dcfea7)

v0.10.4

Compare Source

Bug Fixes

v0.10.3

Compare Source

Bug Fixes

v0.10.2

Compare Source

Features

v0.10.1

Compare Source

Bug Fixes
Features

v0.10.0

Compare Source

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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, click this checkbox.

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

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a4fa53d to 0f8c74e Compare April 27, 2022 10:49
@renovate renovate bot changed the title chore(deps): update devdependency vitest to ^0.10.0 chore(deps): update all non-major dependencies Apr 27, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 963a5a6 to c729987 Compare May 9, 2022 12:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 24d81ac to 1094255 Compare May 16, 2022 05:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from b184d0d to 557dfb3 Compare May 24, 2022 00:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from e2e15fa to bc95f38 Compare June 1, 2022 12:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 6e081d3 to 3af89cb Compare June 6, 2022 11:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 64a8a35 to df995f2 Compare June 15, 2022 12:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 6a93b01 to 8da8f05 Compare June 22, 2022 12:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8da8f05 to b29ab34 Compare June 24, 2022 16:11
@pi0 pi0 merged commit 41dd7cc into main Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant