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 devdependencies #1057

Merged
merged 1 commit into from Jun 11, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 11, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cypress ~10.0.2 -> ~10.1.0 age adoption passing confidence
esbuild ~0.14.42 -> ~0.14.43 age adoption passing confidence
eslint-define-config ~1.5.0 -> ~1.5.1 age adoption passing confidence
lint-staged ~13.0.0 -> ~13.0.1 age adoption passing confidence
vite ~2.9.10 -> ~2.9.12 age adoption passing confidence

Release Notes

cypress-io/cypress

v10.1.0

Compare Source

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

v10.0.3

Compare Source

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

evanw/esbuild

v0.14.43

Compare Source

  • Fix TypeScript parse error whe a generic function is the first type argument (#​2306)

    In TypeScript, the << token may need to be split apart into two < tokens if it's present in a type argument context. This was already correctly handled for all type expressions and for identifier expressions such as in the following code:

    // These cases already worked in the previous release
    let foo: Array<<T>() => T>;
    bar<<T>() => T>;

    However, normal expressions of the following form were previously incorrectly treated as syntax errors:

    // These cases were broken but have now been fixed
    foo.bar<<T>() => T>;
    foo?.<<T>() => T>();

    With this release, these cases now parsed correctly.

  • Fix minification regression with pure IIFEs (#​2279)

    An Immediately Invoked Function Expression (IIFE) is a function call to an anonymous function, and is a way of introducing a new function-level scope in JavaScript since JavaScript lacks a way to do this otherwise. And a pure function call is a function call with the special /* @&#8203;__PURE__ */ comment before it, which tells JavaScript build tools that the function call can be considered to have no side effects (and can be removed if it's unused).

    Version 0.14.9 of esbuild introduced a regression that changed esbuild's behavior when these two features were combined. If the IIFE body contains a single expression, the resulting output still contained that expression instead of being empty. This is a minor regression because you normally wouldn't write code like this, so this shouldn't come up in practice, and it doesn't cause any correctness issues (just larger-than-necessary output). It's unusual that you would tell esbuild "remove this if the result is unused" and then not store the result anywhere, since the result is unused by construction. But regardless, the issue has now been fixed.

    For example, the following code is a pure IIFE, which means it should be completely removed when minification is enabled. Previously it was replaced by the contents of the IIFE but it's now completely removed:

    // Original code
    /* @&#8203;__PURE__ */ (() => console.log(1))()
    
    // Old output (with --minify)
    console.log(1);
    
    // New output (with --minify)
  • Add log messages for indirect require references (#​2231)

    A long time ago esbuild used to warn about indirect uses of require because they break esbuild's ability to analyze the dependencies of the code and cause dependencies to not be bundled, resulting in a potentially broken bundle. However, this warning was removed because many people wanted the warning to be removed. Some packages have code that uses require like this but on a code path that isn't used at run-time, so their code still happens to work even though the bundle is incomplete. For example, the following code will not bundle bindings:

    // Prevent React Native packager from seeing modules required with this
    const nodeRequire = require;
    
    function getRealmConstructor(environment) {
      switch (environment) {
        case "node.js":
        case "electron":
          return nodeRequire("bindings")("realm.node").Realm;
      }
    }

    Version 0.11.11 of esbuild removed this warning, which means people no longer have a way to know at compile time whether their bundle is broken in this way. Now that esbuild has custom log message levels, this warning can be added back in a way that should make both people happy. With this release, there is now a log message for this that defaults to the debug log level, which normally isn't visible. You can either do --log-override:indirect-require=warning to make this log message a warning (and therefore visible) or use --log-level=debug to see this and all other debug log messages.

Shinigami92/eslint-define-config

v1.5.1

Compare Source

diff

  • Update ESLint config type (#​111)
  • Update rules for: [eslint]
okonet/lint-staged

v13.0.1

Compare Source

Bug Fixes
  • correct spelling of "0 files" (f27f1d4)
  • suppress error from process.kill when killing tasks on failure (f2c6bdd)
  • deps: update pidtree@^0.6.0 to fix screen size error in WSL (1a77e42)
  • ignore "No matching pid found" error (cb8a432)
  • prevent possible race condition when killing tasks on failure (bc92aff)
Performance Improvements
  • use EventsEmitter instead of setInterval for killing tasks on failure (c508b46)
vitejs/vite

v2.9.12

Compare Source

v2.9.11

Compare Source


Configuration

📅 Schedule: Branch creation - "before 2am" (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 requested a review from a team as a code owner June 11, 2022 00:45
@renovate renovate bot added the c: dependencies Pull requests that adds/updates a dependency label Jun 11, 2022
@codecov
Copy link

codecov bot commented Jun 11, 2022

Codecov Report

Merging #1057 (16f1c50) into main (a3bbb61) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1057      +/-   ##
==========================================
- Coverage   99.65%   99.64%   -0.02%     
==========================================
  Files        2135     2135              
  Lines      229134   229134              
  Branches      975      970       -5     
==========================================
- Hits       228351   228326      -25     
- Misses        762      787      +25     
  Partials       21       21              
Impacted Files Coverage Δ
src/modules/internet/user-agent.ts 86.37% <0.00%> (-6.38%) ⬇️
src/modules/finance/index.ts 99.31% <0.00%> (-0.69%) ⬇️

@import-brain import-brain added this to the v7 - Current Major milestone Jun 11, 2022
import-brain
import-brain previously approved these changes Jun 11, 2022
@import-brain import-brain requested a review from a team June 11, 2022 02:00
ST-DDT
ST-DDT previously approved these changes Jun 11, 2022
@renovate renovate bot dismissed stale reviews from xDivisionByZerox, ST-DDT, and import-brain via 959ecc3 June 11, 2022 12:48
@renovate renovate bot force-pushed the renovate/devdependencies branch 2 times, most recently from 959ecc3 to 68b7f55 Compare June 11, 2022 14:29
@renovate renovate bot force-pushed the renovate/devdependencies branch from 68b7f55 to 16f1c50 Compare June 11, 2022 14:31
@ST-DDT ST-DDT requested review from a team June 11, 2022 14:32
@Shinigami92 Shinigami92 enabled auto-merge (squash) June 11, 2022 14:40
@Shinigami92 Shinigami92 merged commit 5b3f85a into main Jun 11, 2022
@Shinigami92 Shinigami92 deleted the renovate/devdependencies branch June 11, 2022 14:40
Minozzzi pushed a commit to Minozzzi/faker that referenced this pull request Jul 19, 2022
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: dependencies Pull requests that adds/updates a dependency
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

5 participants