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 #1661

Merged
merged 1 commit into from
Jul 31, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 18, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@edge-runtime/vm (source) 1.1.0-beta.11 -> 1.1.0-beta.23 age adoption passing confidence
@iconify-json/carbon ^1.1.6 -> ^1.1.7 age adoption passing confidence
@types/d3-selection ^3.0.2 -> ^3.0.3 age adoption passing confidence
@types/jsdom ^16.2.14 -> ^16.2.15 age adoption passing confidence
@types/ws ^8.2.2 -> ^8.5.3 age adoption passing confidence
@unocss/reset ^0.44.3 -> ^0.45.1 age adoption passing confidence
@vueuse/core ^8.9.3 -> ^8.9.4 age adoption passing confidence
c8 ^7.11.3 -> ^7.12.0 age adoption passing confidence
codemirror ^5.65.6 -> ^5.65.7 age adoption passing confidence
cypress ^10.3.0 -> ^10.3.1 age adoption passing confidence
d3-graph-controller (source) ^2.2.48 -> ^2.2.51 age adoption passing confidence
esbuild ~0.14.49 -> ~0.14.51 age adoption passing confidence
eslint (source) ^8.19.0 -> ^8.20.0 age adoption passing confidence
happy-dom ^6.0.3 -> ^6.0.4 age adoption passing confidence
local-pkg ^0.4.1 -> ^0.4.2 age adoption passing confidence
mlly ^0.5.4 -> ^0.5.5 age adoption passing confidence
mlly ^0.5.2 -> ^0.5.5 age adoption passing confidence
pnpm (source) 7.5.1 -> 7.8.0 age adoption passing confidence
pnpm (source) 7.5.2 -> 7.8.0 age adoption passing confidence
rollup (source) ^2.77.0 -> ^2.77.2 age adoption passing confidence
rollup (source) ^2.67.2 -> ^2.77.2 age adoption passing confidence
unocss ^0.44.3 -> ^0.45.1 age adoption passing confidence
unplugin-auto-import ^0.9.3 -> ^0.10.3 age adoption passing confidence
unplugin-vue-components ^0.21.1 -> ^0.21.2 age adoption passing confidence
vue-router ^4.1.2 -> ^4.1.3 age adoption passing confidence
workbox-window ^6.5.3 -> ^6.5.4 age adoption passing confidence

Release Notes

vercel/edge-runtime

v1.1.0-beta.23

Compare Source

v1.1.0-beta.22

Compare Source

v1.1.0-beta.21

Compare Source

v1.1.0-beta.20

Compare Source

v1.1.0-beta.19

Compare Source

v1.1.0-beta.18

Compare Source

v1.1.0-beta.17

Compare Source

v1.1.0-beta.16

Compare Source

v1.1.0-beta.15

Compare Source

v1.1.0-beta.14

Compare Source

v1.1.0-beta.13

Compare Source

v1.1.0-beta.12

Compare Source

unocss/unocss

v0.45.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.44.7

Compare Source

No significant changes

    View changes on GitHub

v0.44.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.44.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
vueuse/vueuse

v8.9.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
bcoe/c8

v7.12.0

Compare Source

Features
7.11.3 (2022-05-16)
Bug Fixes
7.11.2 (2022-04-20)
Bug Fixes
  • perf: cache this.exclude.shouldInstrument for improved performance (#​388) (8b36f23)
7.11.1 (2022-04-20)
Bug Fixes
codemirror/basic-setup

v5.65.7

Compare Source

cypress-io/cypress

v10.3.1

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#​10-3-1

DerYeger/d3-graph-controller

v2.2.51

Compare Source

Bug Fixes
  • deps: update all non-major dependencies (6b512a2)

v2.2.50

Compare Source

Bug Fixes
  • deps: update dependency ts-deepmerge to v2.0.4 (3c42ac0)

v2.2.49

Compare Source

Bug Fixes
  • release: schedule release (b2a5582)
evanw/esbuild

v0.14.51

Compare Source

  • Add support for React 17's automatic JSX transform (#​334, #​718, #​1172, #​2318, #​2349)

    This adds support for the new "automatic" JSX runtime from React 17+ to esbuild for both the build and transform APIs.

    New CLI flags and API options:

    • --jsx, jsx — Set this to "automatic" to opt in to this new transform
    • --jsx-dev, jsxDev — Toggles development mode for the automatic runtime
    • --jsx-import-source, jsxImportSource — Overrides the root import for runtime functions (default "react")

    New JSX pragma comments:

    • @jsxRuntime — Sets the runtime (automatic or classic)
    • @jsxImportSource — Sets the import source (only valid with automatic runtime)

    The existing @jsxFragment and @jsxFactory pragma comments are only valid with "classic" runtime.

    TSConfig resolving:
    Along with accepting the new options directly via CLI or API, option inference from tsconfig.json compiler options was also implemented:

    • "jsx": "preserve" or "jsx": "react-native" → Same as --jsx=preserve in esbuild
    • "jsx": "react" → Same as --jsx=transform in esbuild (which is the default behavior)
    • "jsx": "react-jsx" → Same as --jsx=automatic in esbuild
    • "jsx": "react-jsxdev" → Same as --jsx=automatic --jsx-dev in esbuild

    It also reads the value of "jsxImportSource" from tsconfig.json if specified.

    For react-jsx it's important to note that it doesn't implicitly disable --jsx-dev. This is to support the case where a user sets "react-jsx" in their tsconfig.json but then toggles development mode directly in esbuild.

    esbuild vs Babel vs TS vs...

    There are a few differences between the various technologies that implement automatic JSX runtimes. The JSX transform in esbuild follows a mix of Babel's and TypeScript's behavior:

    • When an element has __source or __self props:

      • Babel: Print an error about a deprecated transform plugin
      • TypeScript: Allow the props
      • swc: Hard crash
      • esbuild: Print an error — Following Babel was chosen for this one because this might help people catch configuration issues where JSX files are being parsed by multiple tools
    • Element has an "implicit true" key prop, e.g. <a key />:

      • Babel: Print an error indicating that "key" props require an explicit value
      • TypeScript: Silently omit the "key" prop
      • swc: Hard crash
      • esbuild: Print an error like Babel — This might help catch legitimate programming mistakes
    • Element has spread children, e.g. <a>{...children}</a>

      • Babel: Print an error stating that React doesn't support spread children
      • TypeScript: Use static jsx function and pass children as-is, including spread operator
      • swc: same as Babel
      • esbuild: Same as TypeScript

    Also note that TypeScript has some bugs regarding JSX development mode and the generation of lineNumber and columnNumber values. Babel's values are accurate though, so esbuild's line and column numbers match Babel. Both numbers are 1-based and columns are counted in terms of UTF-16 code units.

    This feature was contributed by @​jgoz.

v0.14.50

Compare Source

  • Emit names in source maps (#​1296)

    The source map specification includes an optional names field that can associate an identifier with a mapping entry. This can be used to record the original name for an identifier, which is useful if the identifier was renamed to something else in the generated code. When esbuild was originally written, this field wasn't widely used, but now there are some debuggers that make use of it to provide better debugging of minified code. With this release, esbuild now includes a names field in the source maps that it generates. To save space, the original name is only recorded when it's different from the final name.

  • Update parser for arrow functions with initial default type parameters in .tsx files (#​2410)

    TypeScript 4.6 introduced a change to the parsing of JSX syntax in .tsx files. Now a < token followed by an identifier and then a = token is parsed as an arrow function with a default type parameter instead of as a JSX element. This release updates esbuild's parser to match TypeScript's parser.

  • Fix an accidental infinite loop with --define substitution (#​2407)

    This is a fix for a regression that was introduced in esbuild version 0.14.44 where certain --define substitutions could result in esbuild crashing with a stack overflow. The problem was an incorrect fix for #​2292. The fix merged the code paths for --define and --jsx-factory rewriting since the value substitution is now the same for both. However, doing this accidentally made --define substitution recursive since the JSX factory needs to be able to match against --define substitutions to integrate with the --inject feature. The fix is to only do one additional level of matching against define substitutions, and to only do this for JSX factories. Now these cases are able to build successfully without a stack overflow.

  • Include the "public path" value in hashes (#​2403)

    The --public-path= configuration value affects the paths that esbuild uses to reference files from other files and is used in various situations such as cross-chunk imports in JS and references to asset files from CSS files. However, it wasn't included in the hash calculations used for file names due to an oversight. This meant that changing the public path setting incorrectly didn't result in the hashes in file names changing even though the contents of the files changed. This release fixes the issue by including a hash of the public path in all non-asset output files.

  • Fix a cross-platform consistency bug (#​2383)

    Previously esbuild would minify 0xFFFF_FFFF_FFFF_FFFF as 0xffffffffffffffff (18 bytes) on arm64 chips and as 18446744073709552e3 (19 bytes) on x86_64 chips. The reason was that the number was converted to a 64-bit unsigned integer internally for printing as hexadecimal, the 64-bit floating-point number 0xFFFF_FFFF_FFFF_FFFF is actually 0x1_0000_0000_0000_0180 (i.e. it's rounded up, not down), and converting float64 to uint64 is implementation-dependent in Go when the input is out of bounds. This was fixed by changing the upper limit for which esbuild uses hexadecimal numbers during minification to 0xFFFF_FFFF_FFFF_F800, which is the next representable 64-bit floating-point number below 0x1_0000_0000_0000_0180, and which fits in a uint64. As a result, esbuild will now consistently never minify 0xFFFF_FFFF_FFFF_FFFF as 0xffffffffffffffff anymore, which means the output should now be consistent across platforms.

  • Fix a hang with the synchronous API when the package is corrupted (#​2396)

    An error message is already thrown when the esbuild package is corrupted and esbuild can't be run. However, if you are using a synchronous call in the JavaScript API in worker mode, esbuild will use a child worker to initialize esbuild once so that the overhead of initializing esbuild can be amortized across multiple synchronous API calls. However, errors thrown during initialization weren't being propagated correctly which resulted in a hang while the main thread waited forever for the child worker to finish initializing. With this release, initialization errors are now propagated correctly so calling a synchronous API call when the package is corrupted should now result in an error instead of a hang.

  • Fix tsconfig.json files that collide with directory names (#​2411)

    TypeScript lets you write tsconfig.json files with extends clauses that refer to another config file using an implicit .json file extension. However, if the config file without the .json extension existed as a directory name, esbuild and TypeScript had different behavior. TypeScript ignores the directory and continues looking for the config file by adding the .json extension while esbuild previously terminated the search and then failed to load the config file (because it's a directory). With this release, esbuild will now ignore exact matches when resolving extends fields in tsconfig.json files if the exact match results in a directory.

  • Add platform to the transform API (#​2362)

    The platform option is mainly relevant for bundling because it mostly affects path resolution (e.g. activating the "browser" field in package.json files), so it was previously only available for the build API. With this release, it has additionally be made available for the transform API for a single reason: you can now set --platform=node when transforming a string so that esbuild will add export annotations for node, which is only relevant when --format=cjs is also present.

    This has to do with an implementation detail of node that parses the AST of CommonJS files to discover named exports when importing CommonJS from ESM. However, this new addition to esbuild's API is of questionable usefulness. Node's loader API (the main use case for using esbuild's transform API like this) actually bypasses the content returned from the loader and parses the AST that's present on the file system, so you won't actually be able to use esbuild's API for this. See the linked issue for more information.

eslint/eslint

v8.20.0

Compare Source

Features

Bug Fixes

  • 30be0ed fix: no-warning-comments rule escapes special RegEx characters in terms (#​16090) (Lachlan Hunt)
  • bfe5e88 fix: ignore spacing before ] and } in comma-spacing (#​16113) (Milos Djermanovic)

Documentation

Chores

  • bbf8df4 chore: Mark autogenerated release blog post as draft (#​16130) (Nicholas C. Zakas)
  • eee4306 chore: update internal lint dependencies (#​16088) (Bryan Mishkin)
  • 9615a42 chore: update formatter examples template to avoid markdown lint error (#​16085) (Milos Djermanovic)
  • 62541ed chore: fix markdown linting error (#​16083) (唯然)
capricorn86/happy-dom

v6.0.4

Compare Source

👷‍♂️ Patch fixes
  • Fixes an issue related to the Response constructor not forwarding it's parameters to the super class. (#​542)
antfu/local-pkg

v0.4.2

Compare Source

Features
unjs/mlly

v0.5.5

Compare Source

pnpm/pnpm

v7.8.0

Compare Source

Minor Changes

  • When publishConfig.directory is set, only symlink it to other workspace projects if publishConfig.linkDirectory is set to true. Otherwise, only use it for publishing #​5115.

Patch Changes

  • Don't incorrectly identify a lockfile out-of-date when the package has a publishConfig.directory field #​5124.
  • Don't crash when a config file contains a setting with an env variable that doesn't exist #​5093.

Our Gold Sponsors

#### Our Silver Sponsors
#### What's Changed * fix: don't incorrectly identify a lockfile out-of-date by @​zkochan in https://github.com/pnpm/pnpm/pull/5126 * feat: publishConfig.linkDirectory by @​zkochan in https://github.com/pnpm/pnpm/pull/5125 * fix: don't crash on a .npmrc with missing env var by @​zkochan in https://github.com/pnpm/pnpm/pull/5127 * chore: fix typo by @​LuciNyan in https://github.com/pnpm/pnpm/pull/5128 #### New Contributors * @​LuciNyan made their first contribution in https://github.com/pnpm/pnpm/pull/5128

Full Changelog: pnpm/pnpm@v7.7.1...v7.8.0

v7.7.1

Compare Source

Patch Changes

  • pnpm should not consider a lockfile out-of-date if auto-install-peers is set to true and the peer dependency is in devDependencies or optionalDependencies #​5080.
  • Don't incorrectly consider a lockfile out-of-date when workspace:^ or workspace:~ version specs are used in a workspace.

Our Gold Sponsors

#### Our Silver Sponsors
#### What's Changed * fix: frozen install in a project with peer deps and `auto-install-peers=true` by @​zkochan in https://github.com/pnpm/pnpm/pull/5120 * fix: don't incorrectly consider a lockfile to be out-of-date by @​zkochan in https://github.com/pnpm/pnpm/pull/5121

Full Changelog: pnpm/pnpm@v7.7.0...v7.7.1

v7.7.0

Compare Source

Minor Changes

  • Add experimental lockfile format that should merge conflict less in the importers section. Enabled by setting the use-inline-specifiers-lockfile-format = true feature flag in .npmrc.

    If this feature flag is committed to a repo, we recommend setting the minimum allowed version of pnpm to this release in the package.json engines field. Once this is set, older pnpm versions will throw on invalid lockfile versions.

  • Add publishDirectory field to the lockfile and relink the project when it changes.

  • verify-store-integrity=false makes pnpm skip checking the integrities of files in the global content-addressable store.

  • Allow to set only-built-dependencies[] through .npmrc.

Patch Changes

  • It should be possible to publish a package with local dependencies from a custom publish directory (set via publishConfig.directory) #​3901.
  • pnpm deploy should inject local dependencies of all types (dependencies, optionalDependencies, devDependencies) #​5078.
  • When a project in a workspace has a publishConfig.directory set, dependent projects should install the project from that directory #​3901
  • pnpm deploy: accept absolute paths and use cwd instead of workspaceDir for deploy target directory #​4980.
  • pnpm setup should update .zshrc in the right directory when a $ZDOTDIR is set.

Our Gold Sponsors

#### Our Silver Sponsors
#### What's Changed * fix(deploy): inject all types of deps by @​zkochan in https://github.com/pnpm/pnpm/pull/5084 * fix(make-dedicated-lockfile): prepublishOnly script is automatically … by @​zkochan in https://github.com/pnpm/pnpm/pull/5083 * fix: symlink a workspace pkg correctly, when it has a custom publish dir by @​zkochan in https://github.com/pnpm/pnpm/pull/5089 * feat: add experimental use-inline-specifiers-lockfile-format by @​gluxon in https://github.com/pnpm/pnpm/pull/5091 * fix: plugin-commands-deploy use path resolve on deploy target dir by @​AWare in https://github.com/pnpm/pnpm/pull/5026 * fix: relink the project when its publish directory changes by @​zkochan in https://github.com/pnpm/pnpm/pull/5109 * fix: don't include specifiers field in new experimental lockfile format by @​zkochan in https://github.com/pnpm/pnpm/pull/5110 * feat: verify-store-integrity by @​zkochan in https://github.com/pnpm/pnpm/pull/5112 #### New Contributors * @​AWare made their first contribution in https://github.com/pnpm/pnpm/pull/5026

Full Changelog: pnpm/pnpm@v7.6.0...v7.7.0

v7.6.0

Compare Source

Minor Changes

  • A new setting supported: prefer-symlinked-executables. When true, pnpm will create symlinks to executables in
    node_modules/.bin instead of command shims (but on POSIX systems only).

    This setting is true by default when node-linker is set to hoisted.

    Related issue: #​4782.

  • When lockfile-include-tarball-url is set to true, every entry in pnpm-lock.yaml will contain the full URL to the package's tarball #​5054.

Patch Changes

  • pnpm deploy should include all dependencies by default #​5035.
  • Don't print warnings about file verifications. Just print info messages instead.
  • pnpm publish --help should print the --recursive and --filter options #​5019.
  • It should be possible to run exec/run/dlx with the --use-node-version option.
  • pnpm deploy should not modify the lockfile #​5071
  • pnpm deploy should not fail in CI #​5071
  • When auto-install-peers is set to `t

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, 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 16 times, most recently from e4bce93 to 87b65ef Compare July 24, 2022 11:45
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from 5082158 to fa77102 Compare July 28, 2022 17:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 7329234 to ac2ada5 Compare July 30, 2022 10:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ac2ada5 to eb3e60d Compare July 31, 2022 11:17
@sheremet-va sheremet-va merged commit ea9f8b8 into main Jul 31, 2022
@sheremet-va sheremet-va deleted the renovate/all-minor-patch branch July 31, 2022 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant