fix(deps): update non-major #148

renovate · 2023-07-17T01:08:29Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/core (source)	`7.22.1` -> `7.22.9`
@babel/preset-env (source)	`7.22.4` -> `7.22.9`
@babel/types (source)	`7.22.4` -> `7.22.5`
@commitlint/cli (source)	`17.6.5` -> `17.6.7`
@commitlint/config-conventional (source)	`17.6.5` -> `17.6.7`
@microsoft/api-extractor (source)	`7.35.2` -> `7.36.3`
@rollup/plugin-commonjs (source)	`25.0.0` -> `25.0.3`
@sanity/semantic-release-preset (source)	`4.1.1` -> `4.1.2`
@types/node (source)	`20.2.5` -> `20.4.4`
@types/uuid (source)	`9.0.1` -> `9.0.2`
@typescript-eslint/eslint-plugin	`5.59.9` -> `5.62.0`
@typescript-eslint/parser	`5.59.9` -> `5.62.0`
browserslist	`4.21.7` -> `4.21.9`
esbuild	`0.18.0` -> `0.18.16`
eslint (source)	`8.42.0` -> `8.45.0`
get-latest-version	`5.0.1` -> `5.1.0`
lint-staged	`13.2.2` -> `13.2.3`
prettier-plugin-packagejson	`2.4.3` -> `2.4.5`
recast	`0.23.2` -> `0.23.3`
rollup (source)	`3.24.0` -> `3.26.3`
rollup-plugin-visualizer	`5.9.0` -> `5.9.2`
semantic-release	`21.0.3` -> `21.0.7`
typescript (source)	`5.1.3` -> `5.1.6`

Release Notes

babel/babel (@babel/core)

`v7.22.9`

Compare Source

🐛 Bug Fix

babel-plugin-transform-typescript
- #15774 fix: Infinity in enums (@liuxingbaoyu)

💅 Polish

babel-generator
- #15757 recordAndTupleSyntaxType defaults to "hash" (@coderaiser)

🏠 Internal

#15748 Migrate to eslint.config.js (@JLHwung)
#15758 Use Prettier 3 stable (@nicolo-ribaudo)

`v7.22.8`

Compare Source

↩️ Revert

babel-core, babel-traverse
- #15754 Revert "Use NodePath#hub as part of the paths cache key" (@nicolo-ribaudo)

`v7.22.7`

Compare Source

🐛 Bug Fix

babel-generator
- #15719 fix: Avoid internally generating negative source maps columns (@liuxingbaoyu)
babel-core, babel-traverse
- #15725 Use NodePath#hub as part of the paths cache key (@nicolo-ribaudo)
Other
- #15747 fix: export meta from eslint-parser/experimental-worker (@JLHwung)

🏠 Internal

babel-core, babel-traverse
- #15702 Refactor visitors merging (@nullableVoidPtr)

`v7.22.6`

Compare Source

🐛 Bug Fix

babel-compat-data, babel-helper-compilation-targets, babel-preset-env
- #15727 Add opera mobile compat data (@JLHwung)
babel-plugin-transform-optional-chaining
- #15739 Fix transform of delete a?.b in function params (@nicolo-ribaudo)
babel-helper-split-export-declaration, babel-plugin-transform-modules-commonjs
- #15736 fix: Default export for duplicate names (@liuxingbaoyu)
babel-compat-data, babel-preset-env
- #15726 update compat-data sources (@JLHwung)
babel-helpers, babel-plugin-proposal-explicit-resource-management, babel-runtime-corejs3, babel-runtime
- #15705 Fix handling of sync error in @@asyncDispose (@nicolo-ribaudo)
babel-standalone
- #15707 fix: Support transforming Explicit Resource Management in stage-2 (@liuxingbaoyu)
babel-core
- #15626 fix: Works correctly with --frozen-intrinsics (@liuxingbaoyu)

🏠 Internal

babel-helper-create-class-features-plugin, babel-plugin-transform-classes
- #15700 Minor class transform cleanups (@JLHwung)

🔬 Output optimization

babel-plugin-bugfix-v8-spread-parameters-in-optional-chaining, babel-plugin-transform-class-properties, babel-plugin-transform-optional-chaining, babel-plugin-transform-typescript
- #15740 Compress output for optional chain with multiple ?. (@nicolo-ribaudo)
babel-plugin-proposal-destructuring-private, babel-plugin-proposal-do-expressions, babel-plugin-proposal-pipeline-operator, babel-plugin-transform-class-properties, babel-plugin-transform-nullish-coalescing-operator, babel-plugin-transform-optional-chaining, babel-plugin-transform-private-property-in-object, babel-traverse
- #15741 Inject tmp vars in the params list of IIFEs when possible (@nicolo-ribaudo)

`v7.22.5`

Compare Source

🐛 Bug Fix

babel-preset-env, babel-standalone
- #15675 Fix using syntax-unicode-sets-regex in standalone (@nicolo-ribaudo)

💅 Polish

babel-core
- #15683 Suggest -transform- when resolving missing plugins (@nicolo-ribaudo)

conventional-changelog/commitlint (@commitlint/cli)

`v17.6.7`

Compare Source

Note: Version bump only for package @commitlint/cli

`v17.6.6`

Compare Source

Note: Version bump only for package @commitlint/cli

conventional-changelog/commitlint (@commitlint/config-conventional)

`v17.6.7`

Compare Source

Note: Version bump only for package @commitlint/config-conventional

`v17.6.6`

Compare Source

Note: Version bump only for package @commitlint/config-conventional

rollup/plugins (@rollup/plugin-commonjs)

`v25.0.3`

Compare Source

2023-07-15

Bugfixes

fix: preserve this reference in the child class #1537

`v25.0.2`

Compare Source

2023-06-19

Bugfixes

fix: add classBodyDepth flag #1507

`v25.0.1`

Compare Source

2023-06-10

Bugfixes

fix: change dynamicRequireRoot to normalizedDynamicRequireRoot && tweak related tests #1508

sanity-io/semantic-release-preset (@sanity/semantic-release-preset)

`v4.1.2`

Compare Source

Bug Fixes

deps: update dependency conventional-changelog-conventionalcommits to v6 (#90) (0d58fdb)
deps: update non-major (#92) (3397e42)

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

eslint-plugin: [ban-types] ban types in extends and implements (#7129) (997783f)
use graphemer instead of grapheme-splitter (#7069) (faea3ff)

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.

`v5.60.1`

Compare Source

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

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

`v5.60.0`

Compare Source

Features

eslint-plugin: [restrict-plus-operands] add allow* options (#6161) (def09f8)

5.59.11 (2023-06-12)

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

5.59.10 (2023-06-12)

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

5.59.9 (2023-06-05)

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

5.59.8 (2023-05-29)

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

5.59.7 (2023-05-22)

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

5.59.6 (2023-05-15)

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

5.59.5 (2023-05-08)

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

5.59.4 (2023-05-08)

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

5.59.3 (2023-05-08)

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

5.59.2 (2023-05-01)

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

5.59.1 (2023-04-24)

Bug Fixes

eslint-plugin: [prefer-regexp-exec] skip malformed regexes (#6935) (05ed60e)
eslint-plugin: [unified-signatures] no parameters function (#6940) (2970861)

`v5.59.11`

Compare Source

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

`v5.59.10`

Compare Source

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

typescript-eslint/typescript-eslint (@typescript-eslint/parser)

`v5.62.0`

Compare Source

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

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

`v5.61.0`

Compare Source

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

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/parser

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

`v5.60.1`

Compare Source

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

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

`v5.60.0`

Compare Source

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

5.59.11 (2023-06-12)

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

5.59.10 (2023-06-12)

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

5.59.9 (2023-06-05)

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

5.59.8 (2023-05-29)

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

5.59.7 (2023-05-22)

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

5.59.6 (2023-05-15)

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

5.59.5 (2023-05-08)

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

5.59.4 (2023-05-08)

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

5.59.3 (2023-05-08)

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

5.59.2 (2023-05-01)

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

5.59.1 (2023-04-24)

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

`v5.59.11`

Compare Source

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

`v5.59.10`

Compare Source

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

browserslist/browserslist (browserslist)

`v4.21.9`

Compare Source

Fixed Opera Mobile edge cases (by Steve Repsher).

`v4.21.8`

Compare Source

Fixed supports query and mobileToDesktop (by Steve Repsher).

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 */
@&#8203;starting-style {
  h1 {
    background-color: transparent;
  }
}

/* Output */
@&#8203;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](https://togithub.com/evanw/esbuild/iss

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

This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

socket-security · 2023-07-17T01:13:19Z

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: @sanity/semantic-release-preset@4.1.1

fix(deps): update non-major

4316f2f

renovate bot requested a review from a team as a code owner July 17, 2023 01:08

renovate bot added 📦 deps 🤖 bot labels Jul 17, 2023

stipsan merged commit dbf0fc0 into main Jul 24, 2023
7 checks passed

stipsan deleted the renovate/non-major branch July 24, 2023 09:03

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update non-major #148

fix(deps): update non-major #148

renovate bot commented Jul 17, 2023 •

edited

socket-security bot commented Jul 17, 2023

fix(deps): update non-major #148

fix(deps): update non-major #148

Conversation

renovate bot commented Jul 17, 2023 • edited

Release Notes

🐛 Bug Fix

💅 Polish

🏠 Internal

↩️ Revert

🐛 Bug Fix

🏠 Internal

🐛 Bug Fix

🏠 Internal

🔬 Output optimization

🐛 Bug Fix

💅 Polish

Bugfixes

Bugfixes

Bugfixes

Bug Fixes

Bug Fixes

Features

Features

5.60.1 (2023-06-26)

Features

5.59.11 (2023-06-12)

5.59.10 (2023-06-12)

5.59.9 (2023-06-05)

5.59.8 (2023-05-29)

5.59.7 (2023-05-22)

5.59.6 (2023-05-15)

5.59.5 (2023-05-08)

5.59.4 (2023-05-08)

5.59.3 (2023-05-08)

5.59.2 (2023-05-01)

5.59.1 (2023-04-24)

Bug Fixes

5.60.1 (2023-06-26)

5.59.11 (2023-06-12)

5.59.10 (2023-06-12)

5.59.9 (2023-06-05)

5.59.8 (2023-05-29)

5.59.7 (2023-05-22)

5.59.6 (2023-05-15)

5.59.5 (2023-05-08)

5.59.4 (2023-05-08)

5.59.3 (2023-05-08)

5.59.2 (2023-05-01)

5.59.1 (2023-04-24)

Configuration

socket-security bot commented Jul 17, 2023

renovate bot commented Jul 17, 2023 •

edited