Skip to content

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

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
Merged
merged 1 commit into from
Jul 25, 2023
Merged

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

merged 1 commit into from
Jul 25, 2023
+1,508 −1,239

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 25, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@swc/core (source) ^1.3.67 -> ^1.3.70 age adoption passing confidence
@swc/jest ^0.2.26 -> ^0.2.27 age adoption passing confidence
@types/jest (source) ^29.5.2 -> ^29.5.3 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.60.1 -> ^5.62.0 age adoption passing confidence
esbuild ^0.18.10 -> ^0.18.16 age adoption passing confidence
eslint (source) ^8.43.0 -> ^8.45.0 age adoption passing confidence
eslint-config-airbnb-typescript ^17.0.0 -> ^17.1.0 age adoption passing confidence
jest (source) ^29.5.0 -> ^29.6.1 age adoption passing confidence

Release Notes

swc-project/swc (@​swc/core)

v1.3.70

Compare Source

Bug Fixes

  • (es/minifier) Fix a bug about eval of name mangler (#​7615) (6be1f70)

  • (es/minifier) Do not reuse identifier used for import bindings (#​7639) (a65be14)

  • (es/module) Skip CJS and AMD transformations for Script (#​7661) (a2d0408)

Features
Testing
Buiild

v1.3.69

Compare Source

Bug Fixes

  • (es/compat) Visit children of while statement in the generator pass (#​7624) (d2ac2c1)

  • (es/compat) Fix loose mode of the spread pass (#​7608) (a7daa5b)

  • (es/minifier) Don't drop unused properties of top-level vars (#​7638) (19ba714)

Features
Miscellaneous Tasks
  • (es/parser) Scope use of lexical to certain features (#​7644) (a961090)
Refactor
Build

v1.3.68

Compare Source

Bug Fixes
Features

  • (es/compat) Implement transform for explicit resource management (#​7376) (bcd5a1d)

  • (es/minifier) Drop unused properties (#​7534) (47d2edd)

  • (es/minifier) Compress common sub expressions in sequences (#​7587) (ff1ad95)

  • (es/optimization) Support default imports for const modules (#​7604) (ac02b84)

Refactor
swc-project/jest (@​swc/jest)

v0.2.27

Compare Source

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

v5.62.0

Compare Source

Bug Fixes
  • eslint-plugin: [comma-spacing] allow no space after trailing comma in objects and arrays (#​6938) (24bdacc)
  • eslint-plugin: [prefer-includes] escape special characters (#​7161) (5a347a5), closes #​7145
  • eslint-plugin: replace auto-fix of class literal property style rule with suggestion (#​7054) (a8c824a)
Features
  • eslint-plugin: [prefer-nullish-coalescing] add ignorePrimitives option (#​6487) (6edaa04)

You can read about our versioning strategy and releases on our website.

v5.61.0

Compare Source

Features

You can read about our versioning strategy and releases on our website.

5.60.1 (2023-06-26)

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

You can read about our versioning strategy and releases on our website.

evanw/esbuild (esbuild)

v0.18.16

Compare Source

  • Fix a regression with whitespace inside :is() (#​3265)

    The change to parse the contents of :is() in version 0.18.14 introduced a regression that incorrectly flagged the contents as a syntax error if the contents started with a whitespace token (for example div:is( .foo ) {}). This regression has been fixed.

v0.18.15

Compare Source

  • Add the --serve-fallback= option (#​2904)

    The web server built into esbuild serves the latest in-memory results of the configured build. If the requested path doesn't match any in-memory build result, esbuild also provides the --servedir= option to tell esbuild to serve the requested path from that directory instead. And if the requested path doesn't match either of those things, esbuild will either automatically generate a directory listing (for directories) or return a 404 error.

    Starting with this release, that last step can now be replaced with telling esbuild to serve a specific HTML file using the --serve-fallback= option. This can be used to provide a "not found" page for missing URLs. It can also be used to implement a single-page app that mutates the current URL and therefore requires the single app entry point to be served when the page is loaded regardless of whatever the current URL is.

  • Use the tsconfig field in package.json during extends resolution (#​3247)

    This release adds a feature from TypeScript 3.2 where if a tsconfig.json file specifies a package name in the extends field and that package's package.json file has a tsconfig field, the contents of that field are used in the search for the base tsconfig.json file.

  • Implement CSS nesting without :is() when possible (#​1945)

    Previously esbuild would always produce a warning when transforming nested CSS for a browser that doesn't support the :is() pseudo-class. This was because the nesting transform needs to generate an :is() in some complex cases which means the transformed CSS would then not work in that browser. However, the CSS nesting transform can often be done without generating an :is(). So with this release, esbuild will no longer warn when targeting browsers that don't support :is() in the cases where an :is() isn't needed to represent the nested CSS.

    In addition, esbuild's nested CSS transform has been updated to avoid generating an :is() in cases where an :is() is preferable but there's a longer alternative that is also equivalent. This update means esbuild can now generate a combinatorial explosion of CSS for complex CSS nesting syntax when targeting browsers that don't support :is(). This combinatorial explosion is necessary to accurately represent the original semantics. For example:

    /* Original code */
.first,
.second,
.third {
  & > & {
    color: red;
  }
}

/* Old output (with --target=chrome80) */
:is(.first, .second, .third) > :is(.first, .second, .third) {
  color: red;
}

/* New output (with --target=chrome80) */
.first > .first,
.first > .second,
.first > .third,
.second > .first,
.second > .second,
.second > .third,
.third > .first,
.third > .second,
.third > .third {
  color: red;
}

    This change means you can now use CSS nesting with esbuild when targeting an older browser that doesn't support :is(). You'll now only get a warning from esbuild if you use complex CSS nesting syntax that esbuild can't represent in that older browser without using :is(). There are two such cases:

    /* Case 1 */
a b {
  .foo & {
    color: red;
  }
}

/* Case 2 */
a {
  > b& {
    color: red;
  }
}

    These two cases still need to use :is(), both for different reasons, and cannot be used when targeting an older browser that doesn't support :is():

    /* Case 1 */
.foo :is(a b) {
  color: red;
}

/* Case 2 */
a > a:is(b) {
  color: red;
}

  • Automatically lower inset in CSS for older browsers

    With this release, esbuild will now automatically expand the inset property to the top, right, bottom, and left properties when esbuild's target is set to a browser that doesn't support inset:

    /* Original code */
.app {
  position: absolute;
  inset: 10px 20px;
}

/* Old output (with --target=chrome80) */
.app {
  position: absolute;
  inset: 10px 20px;
}

/* New output (with --target=chrome80) */
.app {
  position: absolute;
  top: 10px;
  right: 20px;
  bottom: 10px;
  left: 20px;
}

  • Add support for the new @starting-style CSS rule (#​3249)

    This at rule allow authors to start CSS transitions on first style update. That is, you can now make the transition take effect when the display property changes from none to block.

    /* Original code */
@​starting-style {
  h1 {
    background-color: transparent;
  }
}

/* Output */
@​starting-style{h1{background-color:transparent}}

    This was contributed by @​yisibl.

v0.18.14

Compare Source

  • Implement local CSS names (#​20)

    This release introduces two new loaders called global-css and local-css and two new pseudo-class selectors :local() and :global(). This is a partial implementation of the popular CSS modules approach for avoiding unintentional name collisions in CSS. I'm not calling this feature "CSS modules" because although some people in the community call it that, other people in the community have started using "CSS modules" to refer to something completely different and now CSS modules is an overloaded term.

    Here's how this new local CSS name feature works with esbuild:

    • Identifiers that look like .className and #idName are global with the global-css loader and local with the local-css loader. Global identifiers are the same across all files (the way CSS normally works) but local identifiers are different between different files. If two separate CSS files use the same local identifier .button, esbuild will automatically rename one of them so that they don't collide. This is analogous to how esbuild automatically renames JS local variables with the same name in separate JS files to avoid name collisions.

    • It only makes sense to use local CSS names with esbuild when you are also using esbuild's bundler to bundle JS files that import CSS files. When you do that, esbuild will generate one export for each local name in the CSS file. The JS code can import these names and use them when constructing HTML DOM. For example:

      // app.js
import { outerShell } from './app.css'
const div = document.createElement('div')
div.className = outerShell
document.body.appendChild(div)
      /* app.css */
.outerShell {
  position: absolute;
  inset: 0;
}

      When you bundle this with esbuild app.js --bundle --loader:.css=local-css --outdir=out you'll now get this (notice how the local CSS name outerShell has been renamed):

      // out/app.js
(() => {
  // app.css
  var outerShell = "app_outerShell";

  // app.js
  var div = document.createElement("div");
  div.className = outerShell;
  document.body.appendChild(div);
})();
      /* out/app.css */
.app_outerShell {
  position: absolute;
  inset: 0;
}

      This feature only makes sense to use when bundling is enabled both because your code needs to import the renamed local names so that it can use them, and because esbuild needs to be able to process all CSS files containing local names in a single bundling operation so that it can successfully rename conflicting local names to avoid collisions.

    • If you are in a global CSS file (with the global-css loader) you can create a local name using :local(), and if you are in a local CSS file (with the local-css loader) you can create a global name with :global(). So the choice of the global-css loader vs. the local-css loader just sets the default behavior for identifiers, but you can override it on a case-by-case basis as necessary. For example:

      :local(.button) {
  color: red;
}
:global(.button) {
  color: blue;
}

      Processing this CSS file with esbuild with either the global-css or local-css loader will result in something like this:

      .stdin_button {
  color: red;
}
.button {
  color: blue;
}

    • The names that esbuild generates for local CSS names are an implementation detail and are not intended to be hard-coded anywhere. The only way you should be referencing the local CSS names in your JS or HTML is with an import statement in JS that is bundled with esbuild, as demonstrated above. For example, when --minify is enabled esbuild will use a different name generation algorithm which generates names that are as short as possible (analogous to how esbuild minifies local identifiers in JS).

    • You can easily use both global CSS files and local CSS files simultaneously if you give them different file extensions. For example, you could pass --loader:.css=global-css and --loader:.module.css=local-css to esbuild so that .css files still use global names by default but .module.css files use local names by default.

    • Keep in mind that the css loader is different than the global-css loader. The :local and :global annotations are not enabled with the css loader and will be passed through unchanged. This allows you to have the option of using esbuild to process CSS containing while preserving these annotations. It also means that local CSS names are disabled by default for now (since the css loader is currently the default for CSS files). The :local and :global syntax may be enabled by default in a future release.

    Note that esbuild's implementation does not currently have feature parity with other implementations of modular CSS in similar tools. This is only a preliminary release with a partial implementation that includes some basic behavior to get the process started. Additional behavior may be added in future releases. In particular, this release does not implement:

    • The composes pragma
    • Tree shaking for unused local CSS
    • Local names for keyframe animations, grid lines, @container, @counter-style, etc.

    Issue #​20 (the issue for this feature) is esbuild's most-upvoted issue! While this release still leaves that issue open, it's an important first step in that direction.

  • Parse :is, :has, :not, and :where in CSS

    With this release, esbuild will now parse the contents of these pseudo-class selectors as a selector list. This means you will now get syntax warnings within these selectors for invalid selector syntax. It also means that esbuild's CSS nesting transform behaves slightly differently than before because esbuild is now operating on an AST instead of a token stream. For example:

    /* Original code */
div {
  :where(.foo&) {
    color: red;
  }
}

/* Old output (with --target=chrome90) */
:where(.foo:is(div)) {
  color: red;
}

/* New output (with --target=chrome90) */
:where(div.foo) {
  color: red;
}

v0.18.13

Compare Source

  • Add the --drop-labels= option (#​2398)

    If you want to conditionally disable some development-only code and have it not be present in the final production bundle, right now the most straightforward way of doing this is to use the --define: flag along with a specially-named global variable. For example, consider the following code:

    function main() {
  DEV && doAnExpensiveCheck()
}

    You can build this for development and production like this:

    • Development: esbuild --define:DEV=true
    • Production: esbuild --define:DEV=false

    One drawback of this approach is that the resulting code crashes if you don't provide a value for DEV with --define:. In practice this isn't that big of a problem, and there are also various ways to work around this.

    However, another approach that avoids this drawback is to use JavaScript label statements instead. That's what the --drop-labels= flag implements. For example, consider the following code:

    function main() {
  DEV: doAnExpensiveCheck()
}

    With this release, you can now build this for development and production like this:

    • Development: esbuild
    • Production: esbuild --drop-labels=DEV

    This means that code containing optional development-only checks can now be written such that it's safe to run without any additional configuration. The --drop-labels= flag takes comma-separated list of multiple label names to drop.

  • Avoid causing unhandledRejection during shutdown (#​3219)

    All pending esbuild JavaScript API calls are supposed to fail if esbuild's underlying child process is unexpectedly terminated. This can happen if SIGINT is sent to the parent node process with Ctrl+C, for example. Previously doing this could also cause an unhandled promise rejection when esbuild attempted to communicate this failure to its own child process that no longer exists. This release now swallows this communication failure, which should prevent this internal unhandled promise rejection. This change means that you can now use esbuild's JavaScript API with a custom SIGINT handler that extends the lifetime of the node process without esbuild's internals causing an early exit due to an unhandled promise rejection.

  • Update browser compatibility table scripts

    The scripts that esbuild uses to compile its internal browser compatibility table have been overhauled. Briefly:

    • Converted from JavaScript to TypeScript
    • Fixed some bugs that resulted in small changes to the table
    • Added caniuse-lite and @mdn/browser-compat-data as new data sources (replacing manually-copied information)

    This change means it's now much easier to keep esbuild's internal compatibility tables up to date. You can review the table changes here if you need to debug something about this change:

v0.18.12

Compare Source

  • Fix a panic with const enum inside parentheses (#​3205)

    This release fixes an edge case where esbuild could potentially panic if a TypeScript const enum statement was used inside of a parenthesized expression and was followed by certain other scope-related statements. Here's a minimal example that triggers this edge case:

    (() => {
  const enum E { a };
  () => E.a
})

  • Allow a newline in the middle of TypeScript export type statement (#​3225)

    Previously esbuild incorrectly rejected the following valid TypeScript code:

    export type
{ T };

export type
* as foo from 'bar';

    Code that uses a newline after export type is now allowed starting with this release.

  • Fix cross-module inlining of string enums (#​3210)

    A refactoring typo in version 0.18.9 accidentally introduced a regression with cross-module inlining of string enums when combined with computed property accesses. This regression has been fixed.

  • Rewrite .js to .ts inside packages with exports (#​3201)

    Packages with the exports field are supposed to disable node's path resolution behavior that allows you to import a file with a different extension than the one in the source code (for example, importing foo/bar to get foo/bar.js). And TypeScript has behavior where you can import a non-existent .js file and you will get the .ts file instead. Previously the presence of the exports field caused esbuild to disable all extension manipulation stuff which included both node's implicit file extension searching and TypeScript's file extension swapping. However, TypeScript appears to always apply file extension swapping even in this case. So with this release, esbuild will now rewrite .js to .ts even inside packages with exports.

  • Fix a redirect edge case in esbuild's development server (#​3208)

    The development server canonicalizes directory URLs by adding a trailing slash. For example, visiting /about redirects to /about/ if /about/index.html would be served. However, if the requested path begins with two slashes, then the redirect incorrectly turned into a protocol-relative URL. For example, visiting //about redirected to //about/ which the browser turns into http://about/. This release fixes the bug by canonicalizing the URL path when doing this redirect.

eslint/eslint (eslint)

v8.45.0

Compare Source

Features

  • cdd063c feat: Expose LegacyESLint in unsupported API (#​17341) (Nicholas C. Zakas)
  • d34abe5 feat: fix indent rule for else-if (#​17318) (Milos Djermanovic)

Bug Fixes

  • b79b6fb fix: Fix suggestion message in no-useless-escape (#​17339) (Francesco Trotta)
  • c667055 fix: provide unique fix and fix.range objects in lint messages (#​17332) (Milos Djermanovic)

Documentation

  • 89f3225 docs: add playground links to correct and incorrect code blocks (#​17306) (Josh Goldberg ✨)
  • f8892b5 docs: Expand rule option schema docs (#​17198) (Matt Wilkinson)
  • 8bcbf11 docs: Config Migration Guide (#​17230) (Ben Perlmutter)
  • bb30908 docs: Update README (GitHub Actions Bot)
  • 84d243b docs: Update README (GitHub Actions Bot)
  • b762632 docs: Update README (GitHub Actions Bot)
  • 138c096 docs: add more prefer-destructuring examples with array destructuring (#​17330) (Milos Djermanovic)
  • 1fc50a8 docs: max-len rule code and tabWidth as positional arguments (#​17331) (Jesús Leganés-Combarro)

Chores

iamturns/eslint-config-airbnb-typescript (eslint-config-airbnb-typescript)

v17.1.0

Compare Source

Features
facebook/jest (jest)

v29.6.1

Compare Source

Fixes

v29.6.0

Compare Source

Features
  • [jest-circus, jest-snapshot] Add support for snapshot matchers in concurrent tests (#​14139)
  • [jest-cli] Include type definitions to generated config files (#​14078)
  • [jest-snapshot] Support arrays as property matchers (#​14025)
  • [jest-core, jest-circus, jest-reporter, jest-runner] Added support for reporting about start individual test cases using jest-circus (#​14174)
Fixes
  • [jest-circus] Prevent false test failures caused by promise rejections handled asynchronously (#​14110)
  • [jest-config] Handle frozen config object (#​14054)
  • [jest-config] Allow coverageDirectory and collectCoverageFrom in project config (#​14180)
  • [jest-core] Always use workers in watch mode to avoid crashes (#​14059).
  • [jest-environment-jsdom, jest-environment-node] Fix assignment of customExportConditions via testEnvironmentOptions when custom env subclass defines a default value (#​13989)
  • [jest-matcher-utils] Fix copying value of inherited getters (#​14007)
  • [jest-mock] Tweak typings to allow jest.replaceProperty() replace methods (#​14008)
  • [jest-mock] Improve user input validation and error messages of spyOn and replaceProperty methods (#​14087)
  • [jest-runtime] Bind jest.isolateModulesAsync to this (#​14083)
  • [jest-runtime] Forward wrapperLength to the Script constructor as columnOffset for accurate debugging (#​14148)
  • [jest-runtime] Guard _isMockFunction access with in (#​14188)
  • [jest-snapshot] Fix a potential bug when not using prettier and improve performance (#​14036)
  • [@jest/transform] Do not instrument .json modules (#​14048)
  • [jest-worker] Restart a shut down worker before sending it a task (#​14015)
Chore & Maintenance
  • [*] Update semver dependency to get vulnerability fix (#​14262)
  • [docs] Updated documentation for the --runTestsByPath CLI command (#​14004)
  • [docs] Updated documentation regarding the synchronous fallback when asynchronous code transforms are unavailable (#​14056)
  • [docs] Update jest statistics of use and downloads in website Index.

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone Pacific/Auckland, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

Sorry, something went wrong.

@renovate
chore(deps): update all non-major dependencies

Verified

This commit was signed with the committer’s verified signature.
gaborbernat Bernát Gábor
GPG key ID: EEDA44E02406AF79
Verified
Learn about vigilant mode
dfa1e5a
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jul 25, 2023
@codecov-commenter
Copy link

Codecov Report

Patch and project coverage have no change.

Comparison is base (0b03ace) 100.00% compared to head (dfa1e5a) 100.00%.

Additional details and impacted files 
@@            Coverage Diff            @@
##              main      #107   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           24        24           
  Branches         2         2           
=========================================
  Hits            24        24

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Codex- Codex- merged commit 2256e98 into main Jul 25, 2023
@Codex- Codex- deleted the renovate/all-minor-patch branch July 25, 2023 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@codecov-commenter @Codex-