chore(dependency): Update all non-major dependencies (minor)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@codemirror/autocomplete	6.8.1 -> 6.9.0
@codemirror/view	6.14.1 -> 6.16.0
@ladle/react	2.16.1 -> 2.17.2
esbuild	^0.18.6 -> ^0.19.0
eslint (source)	8.45.0 -> 8.46.0
eslint-plugin-import	2.27.5 -> 2.28.0

---

Release Notes

codemirror/autocomplete (@​codemirror/autocomplete)

v6.9.0

Compare Source

New features

Completions may now provide a displayLabel property that overrides the way they are displayed in the completion list.

codemirror/view (@​codemirror/view)

v6.16.0

Compare Source

Bug fixes

Fix an issue that made the gutter not stick in place when the editor was in a right-to-left context.

New features

The new EditorView.coordsForChar method returns the client rectangle for a given character in the editor.

v6.15.3

Compare Source

Bug fixes

Fix another crash regression for compositions before line breaks.

v6.15.2

Compare Source

Bug fixes

Fix the check that made sure compositions are dropped when the selection is moved.

v6.15.1

Compare Source

Bug fixes

Fix a regression that could cause the composition content to be drawn incorrectly.

v6.15.0

Compare Source

Bug fixes

Fix dragging a selection from inside the current selection on macOS.

Fix an issue that could cause the scroll position to jump wildly

Don't try to scroll fixed-positioned elements into view by scrolling their parent elements.

Fix a bug that caused the cursor to be hidden when showing a placeholder that consisted of the empty string.

Resolve some issues where composition could incorrectly affect nearby replaced content.

New features

Key bindings can now set a stopPropagation field to cause the view to stop the key event propagation when it considers the event handled.

tajo/ladle (@​ladle/react)

v2.17.2

Compare Source

Patch Changes

• #​472 d51e5f4 Thanks @​tajo! - Global hotkeys should work from inside of the iframe as well.

v2.17.1

Compare Source

Patch Changes

• #​470 9eb9731 Thanks @​tajo! - Increase chunk size warning

v2.17.0

Compare Source

Minor Changes

• #​468 92ea9b1 Thanks @​tajo! - Ladle is adding a few hotkeys to make your life easier:

  • / or ⌘ cmd ＋ p - Focus search input in the sidebar
  • ⌥ opt ＋ → - Go to the next story
  • ⌥ opt ＋ ← - Go to the previous story
  • ⌥ opt ＋ ↓ - Go to the next component
  • ⌥ opt ＋ ↑ - Go to the previous component
  • c - Toggle controls addon
  • d - Toggle dark mode
  • f - Toggle fullscreen mode
  • w - Toggle width addon
  • r - Toggle right-to-left mode
  • s - Toggle story source addon
  • a - Toggle accessibility addon

  These defaults can be customized through the configuration. Some stories might have utilize their own set of hotkeys. If you want to prevent conflicts with Ladle, you can disable all Ladle shortcuts for a specific story by using the meta parameter:

  export default {
    meta: {
      hotkeys: false,
    },
  };
  Story.meta = {
    hotkeys: false,
  };

evanw/esbuild (esbuild)

v0.19.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.18.0 or ~0.18.0. See npm's documentation about semver for more information.

• Handle import paths containing wildcards (#​56, #​700, #​875, #​976, #​2221, #​2515)

  This release introduces wildcards in import paths in two places:

  • Entry points

    You can now pass a string containing glob-style wildcards such as ./src/*.ts as an entry point and esbuild will search the file system for files that match the pattern. This can be used to easily pass esbuild all files with a certain extension on the command line in a cross-platform way. Previously you had to rely on the shell to perform glob expansion, but that is obviously shell-dependent and didn't work at all on Windows. Note that to use this feature on the command line you will have to quote the pattern so it's passed verbatim to esbuild without any expansion by the shell. Here's an example:

    esbuild --minify "./src/*.ts" --outdir=out

    Specifically the * character will match any character except for the / character, and the /**/ character sequence will match a path separator followed by zero or more path elements. Other wildcard operators found in glob patterns such as ? and [...] are not supported.

  • Run-time import paths

    Import paths that are evaluated at run-time can now be bundled in certain limited situations. The import path expression must be a form of string concatenation and must start with either ./ or ../. Each non-string expression in the string concatenation chain becomes a wildcard. The * wildcard is chosen unless the previous character is a /, in which case the /**/* character sequence is used. Some examples:

    // These two forms are equivalent
    const json1 = await import('./data/' + kind + '.json')
    const json2 = await import(`./data/${kind}.json`)

    This feature works with require(...) and import(...) because these can all accept run-time expressions. It does not work with import and export statements because these cannot accept run-time expressions. If you want to prevent esbuild from trying to bundle these imports, you should move the string concatenation expression outside of the require(...) or import(...). For example:

    // This will be bundled
    const json1 = await import('./data/' + kind + '.json')
    
    // This will not be bundled
    const path = './data/' + kind + '.json'
    const json2 = await import(path)

    Note that using this feature means esbuild will potentially do a lot of file system I/O to find all possible files that might match the pattern. This is by design, and is not a bug. If this is a concern, I recommend either avoiding the /**/ pattern (e.g. by not putting a / before a wildcard) or using this feature only in directory subtrees which do not have many files that don't match the pattern (e.g. making a subdirectory for your JSON files and explicitly including that subdirectory in the pattern).

• Path aliases in tsconfig.json no longer count as packages (#​2792, #​3003, #​3160, #​3238)

  Setting --packages=external tells esbuild to make all import paths external when they look like a package path. For example, an import of ./foo/bar is not a package path and won't be external while an import of foo/bar is a package path and will be external. However, the paths field in tsconfig.json allows you to create import paths that look like package paths but that do not resolve to packages. People do not want these paths to count as package paths. So with this release, the behavior of --packages=external has been changed to happen after the tsconfig.json path remapping step.

• Use the local-css loader for .module.css files by default (#​20)

  With this release the css loader is still used for .css files except that .module.css files now use the local-css loader. This is a common convention in the web development community. If you need .module.css files to use the css loader instead, then you can override this behavior with --loader:.module.css=css.

v0.18.20

Compare Source

• Support advanced CSS @import rules (#​953, #​3137)

  CSS @import statements have been extended to allow additional trailing tokens after the import path. These tokens sort of make the imported file behave as if it were wrapped in a @layer, @supports, and/or @media rule. Here are some examples:

  @​import url(foo.css);
  @​import url(foo.css) layer;
  @​import url(foo.css) layer(bar);
  @​import url(foo.css) layer(bar) supports(display: flex);
  @​import url(foo.css) layer(bar) supports(display: flex) print;
  @​import url(foo.css) layer(bar) print;
  @​import url(foo.css) supports(display: flex);
  @​import url(foo.css) supports(display: flex) print;
  @​import url(foo.css) print;

  You can read more about this advanced syntax here. With this release, esbuild will now bundle @import rules with these trailing tokens and will wrap the imported files in the corresponding rules. Note that this now means a given imported file can potentially appear in multiple places in the bundle. However, esbuild will still only load it once (e.g. on-load plugins will only run once per file, not once per import).

eslint/eslint (eslint)

v8.46.0

Compare Source

Features

• 8a93438 feat: require-unicode-regexp support v flag (#​17402) (SUZUKI Sosuke)
• 1a2f966 feat: no-useless-escape support v flag (#​17420) (Yosuke Ota)
• ee68d1d feat: no-empty-character-class support v flag (#​17419) (Milos Djermanovic)
• 853d32b feat: deprecate no-return-await (#​17417) (Carlos Lopez)
• d4f02e4 feat: no-control-regex support v flag (#​17405) (Yosuke Ota)
• 2a35f3e feat: prefer-named-capture-group support v flag (#​17409) (Yosuke Ota)
• 8ca8b50 feat: Better error message for flat config plugins (#​17399) (Nicholas C. Zakas)
• 509f753 feat: no-misleading-character-class support v flag (#​17406) (Yosuke Ota)
• 3caf514 feat: no-regex-spaces support v flag (#​17407) (Yosuke Ota)
• b7fad2b feat: prefer-regex-literals support v flag (#​17410) (Yosuke Ota)
• a6a3ad4 feat: no-useless-backreference support v flag (#​17408) (Yosuke Ota)
• 94954a7 feat: no-invalid-regexp support v flag (#​17404) (Yosuke Ota)
• 1af6eac feat: adds option for allowing empty object patterns as parameter (#​17365) (Tanuj Kanti)
• cf03104 feat: Improve config error messages (#​17385) (Nicholas C. Zakas)

Bug Fixes

• 9803c7c fix: FlatESLint#getRulesMetaForResults shouldn't throw on unknown rules (#​17393) (Milos Djermanovic)
• 42faa17 fix: Update no-loop-func to not overlap with no-undef (#​17358) (Matt Wilkinson)

Documentation

• 4d474e3 docs: update with TypeScript info (#​17423) (James)
• 091f44e docs: File extension named processor deprecation (#​17362) (Matt Wilkinson)
• 9254a6c docs: Update README (GitHub Actions Bot)
• 6d6dc51 docs: fix overlapping of open in playground button (#​17403) (Tanuj Kanti)
• 7fc3a2c docs: Add private class features info to no-underscore-dangle (#​17386) (Matt Wilkinson)
• da73e58 docs: Migrating eslint-env configuration comments (#​17390) (Francesco Trotta)
• 80dffed docs: fix Ignoring Files section in config migration guide (#​17392) (Milos Djermanovic)
• 8a9abb7 docs: Update README (GitHub Actions Bot)
• 7e9be4b docs: Update README (GitHub Actions Bot)
• 0b0bbe0 docs: Update README (GitHub Actions Bot)

Chores

• d1eb7e4 chore: Update ecosystem dependencies (#​17427) (Nicholas C. Zakas)
• fab9e97 chore: package.json update for eslint-config-eslint release (ESLint Jenkins)
• 6246711 chore: package.json update for @​eslint/js release (ESLint Jenkins)
• 0aa0bc3 chore: Add PRs to triage project (#​17421) (Nicholas C. Zakas)

import-js/eslint-plugin-import (eslint-plugin-import)

v2.28.0

Compare Source

Fixed

• [no-duplicates]: remove duplicate identifiers in duplicate imports ([#​2577], thanks [@​joe-matsec])
• [consistent-type-specifier-style]: fix accidental removal of comma in certain cases ([#​2754], thanks [@​bradzacher])
• [Perf] ExportMap: Improve ExportMap.for performance on larger codebases ([#​2756], thanks [@​leipert])
• [no-extraneous-dependencies]/TypeScript: do not error when importing inline type from dev dependencies ([#​1820], thanks [@​andyogo])
• [newline-after-import]/TypeScript: do not error when re-exporting a namespaced import ([#​2832], thanks [@​laurens-dg])
• [order]: partial fix for [#​2687] (thanks [@​ljharb])
• [no-duplicates]: Detect across type and regular imports ([#​2835], thanks [@​benkrejci])
• [extensions]: handle . and .. properly ([#​2778], thanks [@​benasher44])
• [no-unused-modules]: improve schema (thanks [@​ljharb])
• [no-unused-modules]: report error on binding instead of parent export ([#​2842], thanks [@​Chamion])

Changed

• [Docs] [no-duplicates]: fix example schema ([#​2684], thanks [@​simmo])
• [Docs] [group-exports]: fix syntax highlighting ([#​2699], thanks [@​devinrhode2])
• [Docs] [extensions]: reference node ESM behavior ([#​2748], thanks [@​xM8WVqaG])
• [Refactor] [exports-last]: use array.prototype.findlastindex (thanks [@​ljharb])
• [Refactor] [no-anonymous-default-export]: use object.fromentries (thanks [@​ljharb])
• [Refactor] [no-unused-modules]: use array.prototype.flatmap (thanks [@​ljharb])

---

Configuration

📅 Schedule: Branch creation - "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]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/esbuild
npm ERR!   dev esbuild@"^0.19.0" from the root project
npm ERR!   peer esbuild@">= 0.14.0" from [email protected]
npm ERR!   node_modules/esbuild-plugin-copy
npm ERR!     dev esbuild-plugin-copy@"^2.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer esbuild@"^0.18.0" from [email protected]
npm ERR! node_modules/esbuild-sass-plugin
npm ERR!   dev esbuild-sass-plugin@"^2.10.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/esbuild
npm ERR!   peer esbuild@"^0.18.0" from [email protected]
npm ERR!   node_modules/esbuild-sass-plugin
npm ERR!     dev esbuild-sass-plugin@"^2.10.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/e186f5/0040f2/cache/others/npm/_logs/2023-08-10T22_53_45_718Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/e186f5/0040f2/cache/others/npm/_logs/2023-08-10T22_53_45_718Z-debug-0.log

[renovate]

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.