Skip to content
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.

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

Merged
merged 1 commit into from
Dec 19, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 15, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rollup/plugin-replace (source) ^5.0.1 -> ^5.0.2 age adoption passing confidence
@types/node (source) ^18.11.15 -> ^18.11.17 age adoption passing confidence
esbuild ^0.16.7 -> ^0.16.9 age adoption passing confidence
eslint (source) ^8.29.0 -> ^8.30.0 age adoption passing confidence
fork-ts-checker-webpack-plugin ^7.2.13 -> ^7.2.14 age adoption passing confidence
ignore ^5.2.1 -> ^5.2.2 age adoption passing confidence
nitropack 2.0.0-27850417.cbcd068 -> 2.0.0-27851797.fc75d47 age adoption passing confidence
playwright (source) ^1.28.1 -> ^1.29.0 age adoption passing confidence
rollup (source) ^3.7.4 -> ^3.7.5 age adoption passing confidence
vite (source) ~4.0.1 -> ~4.0.2 age adoption passing confidence
vite (source) ^4.0.1 -> ^4.0.2 age adoption passing confidence
vue-tsc ^1.0.13 -> ^1.0.14 age adoption passing confidence

Release Notes

rollup/plugins

v5.0.2

Compare Source

2022-12-17

Bugfixes
evanw/esbuild

v0.16.9

Compare Source

  • Update to Unicode 15.0.0

    The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 14.0.0 to the newly-released Unicode version 15.0.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read https://www.unicode.org/versions/Unicode15.0.0/#Summary for more information about the changes.

  • Disallow duplicate lexically-declared names in nested blocks and in strict mode

    In strict mode or in a nested block, it's supposed to be a syntax error to declare two symbols with the same name unless all duplicate entries are either function declarations or all var declarations. However, esbuild was overly permissive and allowed this when duplicate entries were either function declarations or var declarations (even if they were mixed). This check has now been made more restrictive to match the JavaScript specification:

    // JavaScript allows this
    var a
    function a() {}
    {
      var b
      var b
      function c() {}
      function c() {}
    }
    
    // JavaScript doesn't allow this
    {
      var d
      function d() {}
    }
  • Add a type declaration for the new empty loader (#​2755)

    I forgot to add this in the previous release. It has now been added.

    This fix was contributed by @​fz6m.

  • Add support for the v flag in regular expression literals

    People are currently working on adding a v flag to JavaScript regular expresions. You can read more about this flag here: https://v8.dev/features/regexp-v-flag. This release adds support for parsing this flag, so esbuild will now no longer consider regular expression literals with this flag to be a syntax error. If the target is set to something other than esnext, esbuild will transform regular expression literals containing this flag into a new RegExp() constructor call so the resulting code doesn't have a syntax error. This enables you to provide a polyfill for RegExp that implements the v flag to get your code to work at run-time. While esbuild doesn't typically adopt proposals until they're already shipping in a real JavaScript run-time, I'm adding it now because a) esbuild's implementation doesn't need to change as the proposal evolves, b) this isn't really new syntax since regular expression literals already have flags, and c) esbuild's implementation is a trivial pass-through anyway.

  • Avoid keeping the name of classes with static name properties

    The --keep-names property attempts to preserve the original value of the name property for functions and classes even when identifiers are renamed by the minifier or to avoid a name collision. This is currently done by generating code to assign a string to the name property on the function or class object. However, this should not be done for classes with a static name property since in that case the explicitly-defined name property overwrites the automatically-generated class name. With this release, esbuild will now no longer attempt to preserve the name property for classes with a static name property.

v0.16.8

Compare Source

  • Allow plugins to resolve injected files (#​2754)

    Previously paths passed to the inject feature were always interpreted as file system paths. This meant that onResolve plugins would not be run for them and esbuild's default path resolver would always be used. This meant that the inject feature couldn't be used in the browser since the browser doesn't have access to a file system. This release runs paths passed to inject through esbuild's full path resolution pipeline so plugins now have a chance to handle them using onResolve callbacks. This makes it possible to write a plugin that makes esbuild's inject work in the browser.

  • Add the empty loader (#​1541, #​2753)

    The new empty loader tells esbuild to pretend that a file is empty. So for example --loader:.css=empty effectively skips all imports of .css files in JavaScript so that they aren't included in the bundle, since import "./some-empty-file" in JavaScript doesn't bundle anything. You can also use the empty loader to remove asset references in CSS files. For example --loader:.png=empty causes esbuild to replace asset references such as url(image.png) with url() so that they are no longer included in the resulting style sheet.

  • Fix </script> and </style> escaping for non-default targets (#​2748)

    The change in version 0.16.0 to give control over </script> escaping via --supported:inline-script=false or --supported:inline-script=true accidentally broke automatic escaping of </script> when an explicit target setting is specified. This release restores the correct automatic escaping of </script> (which should not depend on what target is set to).

  • Enable the exports field with NODE_PATHS (#​2752)

    Node has a rarely-used feature where you can extend the set of directories that node searches for packages using the NODE_PATHS environment variable. While esbuild supports this too, previously it only supported the old main field path resolution but did not support the new exports field package resolution. This release makes the path resolution rules the same again for both node_modules directories and NODE_PATHS directories.

eslint/eslint

v8.30.0

Compare Source

Features

Bug Fixes

  • 1a327aa fix: Ensure flat config unignores work consistently like eslintrc (#​16579) (Nicholas C. Zakas)
  • 9b8bb72 fix: autofix recursive functions in no-var (#​16611) (Milos Djermanovic)

Documentation

Chores

TypeStrong/fork-ts-checker-webpack-plugin

v7.2.14

Compare Source

kaelzhang/node-ignore

v5.2.2

Compare Source

unjs/nitro

v2.0.0-27851797.fc75d47

Compare Source

Microsoft/playwright

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();
  • 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
rollup/rollup

v3.7.5

Compare Source

2022-12-17

Bug Fixes
  • Avoid name shadowing when default exporting a class that matches the name of another class (#​4756)
  • Do not display the error message both in a separate line and in the stack trace in rollup CLI (#​4749)
  • Make type of RollupWarning.cause compatible with Error.cause (#​4757)
  • Do not swallow side effects when interacting with modules namespaces nested in another object (#​4758)
Pull Requests
vitejs/vite

v4.0.2

Compare Source

johnsoncodehk/volar

v1.0.14

Compare Source

  • feat: add angular language server example (#​2215)
  • feat(vue-tsc): support for hook api (#​2217)
  • feat: add vue-tsc-eslint-hook module to support use eslint in vue-tsc (#​2220)
  • feat: add setting volar.vueserver.maxFileSize (#​2186)
  • feat: add setting volar.doctor.checkVueTsc and disable by default (#​2186)
  • feat: add setting volar.vueserver.configFilePath (#​2078)
  • feat: auto add space between double curly brackets (#​2088)
  • feat: support formatting for style v-bind (#​2105)
  • fix: virtual code mapping ignored offset 0 (#​2052)
  • fix: auto complete ref value with '.value' not working (#​2203)
  • fix: template AST broken by slot name incremental update (#​2207)
  • fix: preview not working for Vite v4 (#​2198)
Special Sponsor
Out Gold Sponsors
Out Silver Sponsors

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, check this box

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

@codesandbox
Copy link

codesandbox bot commented Dec 15, 2022

CodeSandbox logoCodeSandbox logo  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from aab561a to 442a588 Compare December 16, 2022 01:32
@renovate renovate bot changed the title chore(deps): update devdependency nitropack to v2.0.0-27851797.fc75d47 chore(deps): update all non-major dependencies Dec 16, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 1625ff4 to afa4a8b Compare December 17, 2022 08:27
@renovate renovate bot changed the title chore(deps): update all non-major dependencies Update all non-major dependencies Dec 17, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from afa4a8b to 6213f6e Compare December 17, 2022 16:23
@renovate renovate bot changed the title Update all non-major dependencies chore(deps): update all non-major dependencies Dec 17, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6213f6e to 63d3d44 Compare December 17, 2022 22:22
@vercel
Copy link

vercel bot commented Dec 17, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
framework 🔄 Building (Inspect) Dec 17, 2022 at 10:22PM (UTC)

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 866a89e to 0bf172f Compare December 18, 2022 12:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0bf172f to ab0daba Compare December 19, 2022 10:09
@pi0 pi0 merged commit cd07957 into main Dec 19, 2022
@pi0 pi0 deleted the renovate/all-minor-patch branch December 19, 2022 11:57
@danielroe danielroe added the 3.x label Jan 19, 2023
danielroe pushed a commit that referenced this pull request Jan 21, 2023
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants