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 non-major dependencies #568

Merged
merged 2 commits into from
Jan 3, 2023
Merged

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

merged 2 commits into from
Jan 3, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 2, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ^18.11.17 -> ^18.11.18 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.47.0 -> ^5.48.0 age adoption passing confidence
@typescript-eslint/parser ^5.47.0 -> ^5.48.0 age adoption passing confidence
carbon-components-svelte ^0.70.13 -> ^0.71.0 age adoption passing confidence
esbuild ^0.16.10 -> ^0.16.13 age adoption passing confidence
eslint (source) ^8.30.0 -> ^8.31.0 age adoption passing confidence
eslint-config-prettier ^8.5.0 -> ^8.6.0 age adoption passing confidence
husky (source) ^8.0.2 -> ^8.0.3 age adoption passing confidence
playwright-core (source) 1.28.1 -> 1.29.1 age adoption passing confidence
pnpm (source) 7.19.0 -> 7.22.0 age adoption passing confidence
vite (source) ^4.0.3 -> ^4.0.4 age adoption passing confidence
vitest ^0.26.2 -> ^0.26.3 age adoption passing confidence

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.48.0

Compare Source

Features
  • eslint-plugin: specify which method is unbound and added test case (#​6281) (cf3ffdd)

5.47.1 (2022-12-26)

Bug Fixes
  • ast-spec: correct some incorrect ast types (#​6257) (0f3f645)
  • eslint-plugin: [member-ordering] correctly invert optionalityOrder (#​6256) (ccd45d4)

v5.47.1

Compare Source

Bug Fixes
  • ast-spec: correct some incorrect ast types (#​6257) (0f3f645)
  • eslint-plugin: [member-ordering] correctly invert optionalityOrder (#​6256) (ccd45d4)
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.48.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

5.47.1 (2022-12-26)

Note: Version bump only for package @​typescript-eslint/parser

v5.47.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

carbon-design-system/carbon-components-svelte

v0.71.0

Compare Source

Breaking Changes

  • Select: rename dispatched change event to update
  • Select: forward change event
  • PaginationNav: use 1-indexing to be consistent with Pagination
  • InlineNotification: remove iconDescription prop (replaced with closeButtonDescription and statusIconDescription)

Features

  • Pagination: dispatch change event when user interacts with previous/next buttons, or page/page size dropdowns
  • InlineNotification: add iconDescription and closeButtonDescription props

Documentation

  • link 'source code' to folder for multiple components
  • PaginationNav: add description for change event
evanw/esbuild

v0.16.13

Compare Source

  • Publish a new bundle visualization tool

    While esbuild provides bundle metadata via the --metafile flag, previously esbuild left analysis of it completely up to third-party tools (well, outside of the rudimentary --analyze flag). However, the esbuild website now has a built-in bundle visualization tool:

    You can pass --metafile to esbuild to output bundle metadata, then upload that JSON file to this tool to visualize your bundle. This is helpful for answering questions such as:

    • Which packages are included in my bundle?
    • How did a specific file get included?
    • How small did a specific file compress to?
    • Was a specific file tree-shaken or not?

    I'm publishing this tool because I think esbuild should provide some answer to "how do I visualize my bundle" without requiring people to reach for third-party tools. At the moment the tool offers two types of visualizations: a radial "sunburst chart" and a linear "flame chart". They serve slightly different but overlapping use cases (e.g. the sunburst chart is more keyboard-accessible while the flame chart is easier with the mouse). This tool may continue to evolve over time.

  • Fix --metafile and --mangle-cache with --watch (#​1357)

    The CLI calls the Go API and then also writes out the metafile and/or mangle cache JSON files if those features are enabled. This extra step is necessary because these files are returned by the Go API as in-memory strings. However, this extra step accidentally didn't happen for all builds after the initial build when watch mode was enabled. This behavior used to work but it was broken in version 0.14.18 by the introduction of the mangle cache feature. This release fixes the combination of these features, so the metafile and mangle cache features should now work with watch mode. This behavior was only broken for the CLI, not for the JS or Go APIs.

  • Add an original field to the metafile

    The metadata file JSON now has an additional field: each import in an input file now contains the pre-resolved path in the original field in addition to the post-resolved path in the path field. This means it's now possible to run certain additional analysis over your bundle. For example, you should be able to use this to detect when the same package subpath is represented multiple times in the bundle, either because multiple versions of a package were bundled or because a package is experiencing the dual-package hazard.

v0.16.12

Compare Source

  • Loader defaults to js for extensionless files (#​2776)

    Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

    • CLI:

      esbuild --bundle --loader:=css

    • JS:

      esbuild.build({
  bundle: true,
  loader: { '': 'css' },
})

    • Go:

      api.Build(api.BuildOptions{
  Bundle: true,
  Loader: map[string]api.Loader{"": api.LoaderCSS},
})

    In addition, the "type" field in package.json files now only applies to files with an explicit .js, .jsx, .ts, or .tsx extension. Previously it was incorrectly applied by esbuild to all files that had an extension other than .mjs, .mts, .cjs, or .cts including extensionless files. So for example an extensionless file in a "type": "module" package is now treated as CommonJS instead of ESM.

v0.16.11

Compare Source

  • Avoid a syntax error in the presence of direct eval (#​2761)

    The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:

    // Original code
if (true) {
  function foo() {}
  console.log(!!foo)
  foo = null
  console.log(!!foo)
}
console.log(!!foo)

// Transformed code
if (true) {
  let foo2 = function() {
  };
  var foo = foo2;
  console.log(!!foo2);
  foo2 = null;
  console.log(!!foo2);
}
console.log(!!foo);

    In the above example, the original code should print true false true because it's not run in strict mode (it doesn't contain "use strict" and is not an ES module). The code that esbuild generates has been transformed such that it prints true false true regardless of whether it's run in strict mode or not.

    However, this transformation is impossible if the code contains direct eval because direct eval "poisons" all containing scopes by preventing anything in those scopes from being renamed. That prevents esbuild from splitting up accesses to foo into two separate variables with different names. Previously esbuild still did this transformation but with two variables both named foo, which is a syntax error. With this release esbuild will now skip doing this transformation when direct eval is present to avoid generating code with a syntax error. This means that the generated code may no longer behave as intended since the behavior depends on the run-time strict mode setting instead of the strict mode setting present in the original source code. To fix this problem, you will need to remove the use of direct eval.

  • Fix a bundling scenario involving multiple symlinks (#​2773, #​2774)

    This release contains a fix for a bundling scenario involving an import path where multiple path segments are symlinks. Previously esbuild was unable to resolve certain import paths in this scenario, but these import paths should now work starting with this release. This fix was contributed by @​onebytegone.

eslint/eslint

v8.31.0

Compare Source

Features

  • 52c7c73 feat: check assignment patterns in no-underscore-dangle (#​16693) (Milos Djermanovic)
  • b401cde feat: add options to check destructuring in no-underscore-dangle (#​16006) (Morten Kaltoft)
  • 30d0daf feat: group properties with values in parentheses in key-spacing (#​16677) (Francesco Trotta)

Bug Fixes

  • 35439f1 fix: correct syntax error in prefer-arrow-callback autofix (#​16722) (Francesco Trotta)
  • 87b2470 fix: new instance of FlatESLint should load latest config file version (#​16608) (Milos Djermanovic)

Documentation

Chores

prettier/eslint-config-prettier

v8.6.0

Compare Source

  • Added: [vue/multiline-ternary]. Thanks to @​xcatliu!
typicode/husky

v8.0.3

Compare Source

  • fix: add git not installed message #​1208
Microsoft/playwright

v1.29.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/18928 - [BUG] Electron firstWindow times out after upgrading to 1.28.0https://github.com/microsoft/playwright/issues/192466 - [BUG] Electron firstWindow times out after upgrading to 1.28.https://github.com/microsoft/playwright/issues/1941212 - [REGRESSION]: 1.28 does not work with electron-serve anymorhttps://github.com/microsoft/playwright/issues/19540540 - [BUG] electron.app.getAppPath() returns the path one level higher if you run electron pointing to the directhttps://github.com/microsoft/playwright/issues/195489548 - [REGRESSION]: Ubuntu 18 LTS not supported anymore

Browser Versions

  • Chromium 109.0.5414.46
  • Mozilla Firefox 107.0
  • WebKit 16.4

This version was also tested against the following stable channels:

  • Google Chrome 108
  • Microsoft Edge 108

v1.29.0

Compare Source

New APIs

  • New method route.fetch() and new option json for route.fulfill():

    await page.route('**/api/settings', async route => {
  // Fetch original settings.
  const response = await route.fetch();

  // Force settings theme to a predefined value.
  const json = await response.json();
  json.theme = 'Solorized';

  // Fulfill with modified data.
  await route.fulfill({ json });
});

  • New method locator.all() to iterate over all matching elements:

    // Check all checkboxes!
const checkboxes = page.getByRole('checkbox');
for (const checkbox of await checkboxes.all())
  await checkbox.check();

  • Locator.selectOption matches now by value or label:

    <select multiple>
  <option value="red">Red</div>
  <option value="green">Green</div>
  <option value="blue">Blue</div>
</select>
    await element.selectOption('Red');

  • Retry blocks of code until all assertions pass:

    await expect(async () => {
  const response = await page.request.get('https://api.example.com');
  await expect(response).toBeOK();
}).toPass();

    Read more in our documentation.

  • Automatically capture full page screenshot on test failure:

    // playwright.config.ts
import type { PlaywrightTestConfig } from '@&#8203;playwright/test';

const config: PlaywrightTestConfig = {
  use: {
    screenshot: {
      mode: 'only-on-failure',
      fullPage: true,
    }
  }
};

export default config;

Miscellaneous

Browser Versions

  • Chromium 109.0.5414.46
  • Mozilla Firefox 107.0
  • WebKit 16.4

This version was also tested against the following stable channels:

  • Google Chrome 108
  • Microsoft Edge 108
pnpm/pnpm

v7.22.0

Compare Source

Minor Changes

  • The pnpm list and pnpm why commands will now look through transitive dependencies of workspace: packages. A new --only-projects flag is available to only print workspace: packages.
  • pnpm exec and pnpm run command support --resume-from option. When used, the command will executed from given package #​4690.
  • Expose the npm_command environment variable to lifecycle hooks & scripts.

Patch Changes

  • Fix a situation where pnpm list and pnpm why may not respect the --depth argument.
  • Report to the console when a git-hosted dependency is built #​5847.
  • Throw an accurate error message when trying to install a package that has no versions, or all of its versions are unpublished #​5849.
  • replace dependency is-ci by ci-info (is-ci is just a simple wrapper around ci-info).
  • Only run prepublish scripts of git-hosted dependencies, if the dependency doesn't have a main file. In this case we can assume that the dependencies has to be built.
  • Print more contextual information when a git-hosted package fails to be prepared for installation #​5847.

Our Gold Sponsors

Our Silver Sponsors

v7.21.0

Compare Source

Minor Changes

  • The pnpm dlx command supports the --shell-mode (or -c) option. When used, the script is executed by a shell #​5679.

Patch Changes

  • The config command should work with the --location=global CLI option #​5841.
  • Only the pnpm add --global <pkg> command should fail if there is no global pnpm bin directory in the system PATH #​5841.

Our Gold Sponsors

Our Silver Sponsors

v7.20.0

Compare Source

Minor Changes

  • pnpm gets its own implementation of the following commands:

    • pnpm config get
    • pnpm config set
    • pnpm config delete
    • pnpm config list

    In previous versions these commands were passing through to npm CLI.

    PR: #​5829
    Related issue: #​5621

  • Add show alias to pnpm view #​5835.

  • pnpm reads settings from its own global configuration file at $XDG_CONFIG_HOME/pnpm/rc #​5829.

  • Add the 'description'-field to the licenses output #​5836.

Patch Changes
  • pnpm rebuild should not fail if node_modules was created by pnpm version 7.18 or older #​5815.
  • pnpm env should print help.
  • Run the prepublish scripts of packages installed from Git #​5826.
  • pnpm rebuild should print a better error message when a hoisted dependency is not found #​5815.
Our Gold Sponsors
Our Silver Sponsors
vitejs/vite

v4.0.4

Compare Source

vitest-dev/vitest

v0.26.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - "before 3am 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 added the dependencies label Jan 2, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 9d82643 to 0b36f11 Compare January 3, 2023 10:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0b36f11 to 0128603 Compare January 3, 2023 14:35
@renovate
Copy link
Contributor Author

renovate bot commented Jan 3, 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.

@dominikg dominikg merged commit bc7f03f into main Jan 3, 2023
@dominikg dominikg deleted the renovate/all-minor-patch branch January 3, 2023 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dominikg dominikg dominikg approved these changes

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

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