Aims to give you a break down on stats from encounters to be able to look back and plan future enounters. Also to give the players a nice lookback at events that occured in a story format.
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v8.2.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#820-2024-08-19)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v8.1.0...v8.2.0)
##### 🚀 Features
- **eslint-plugin:** add suggestion to `require-await` to remove `async` keyword
##### 🩹 Fixes
- **eslint-plugin:** \[use-unknown-in-catch-callback-variable] flag second argument of `.then`
- **eslint-plugin:** \[no-unnecessary-type-assertion] conflict with TS for variables used before assignment
- **eslint-plugin:** delete \[] in message if ReadOnly\ is detected
- **eslint-plugin:** \[no-redundant-type-constituents] differentiate a types-error any from a true any
- **eslint-plugin:** \[no-unnecessary-type-parameters] check mapped constraint types if necessary
- **eslint-plugin:** \[no-unsafe-enum-comparison] add logic to see through intersections
##### ❤️ Thank You
- Abraham Guo
- Dave
- Jake Bailey
- James
- Josh Goldberg ✨
- liuxingbaoyu
- Yukihiro Hasegawa
- Yutong Zhu
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v8.2.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#820-2024-08-19)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v8.1.0...v8.2.0)
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
iamkun/dayjs (dayjs)
### [`v1.11.13`](https://togithub.com/iamkun/dayjs/compare/v1.11.12...93c8fd0f807b8a8252f4cd65083bb1d6a49b90e7)
[Compare Source](https://togithub.com/iamkun/dayjs/compare/v1.11.12...v1.11.13)
evanw/esbuild (esbuild)
### [`v0.23.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0231)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.23.0...v0.23.1)
- Allow using the `node:` import prefix with `es*` targets ([#3821](https://togithub.com/evanw/esbuild/issues/3821))
The [`node:` prefix on imports](https://nodejs.org/api/esm.html#node-imports) is an alternate way to import built-in node modules. For example, `import fs from "fs"` can also be written `import fs from "node:fs"`. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with `--target=node14` so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as `--target=node18,es2022` removes the `node:` prefix because none of the `es*` targets are known to support this feature. This release adds the support for the `node:` flag to esbuild's internal compatibility table for `es*` to allow you to use compound targets like this:
```js
// Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;
```
- Fix a panic when using the CLI with invalid build flags if `--analyze` is present ([#3834](https://togithub.com/evanw/esbuild/issues/3834))
Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the `--analyze` flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how `--analyze` is implemented) to a null build object. The panic has been fixed in this release.
- Fix incorrect location of certain error messages ([#3845](https://togithub.com/evanw/esbuild/issues/3845))
This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.
- Print comments before case clauses in switch statements ([#3838](https://togithub.com/evanw/esbuild/issues/3838))
With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).
- Fix a memory leak with `pluginData` ([#3825](https://togithub.com/evanw/esbuild/issues/3825))
With this release, the build context's internal `pluginData` cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return `pluginData` objects from `onResolve` and/or `onLoad` callbacks.
nodejs/node (node)
### [`v20.17.0`](https://togithub.com/nodejs/node/compare/v20.16.0...v20.17.0)
[Compare Source](https://togithub.com/nodejs/node/compare/v20.16.0...v20.17.0)
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), 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 contains the following updates:
20.14.15->20.16.18.1.0->8.2.08.1.0->8.2.01.11.12->1.11.130.23.0->0.23.120.16.0->20.17.0Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v8.2.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#820-2024-08-19) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v8.1.0...v8.2.0) ##### 🚀 Features - **eslint-plugin:** add suggestion to `require-await` to remove `async` keyword ##### 🩹 Fixes - **eslint-plugin:** \[use-unknown-in-catch-callback-variable] flag second argument of `.then` - **eslint-plugin:** \[no-unnecessary-type-assertion] conflict with TS for variables used before assignment - **eslint-plugin:** delete \[] in message if ReadOnly\typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v8.2.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#820-2024-08-19) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v8.1.0...v8.2.0) This was a version bump only for parser to align it with other projects, there were no code changes. You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.iamkun/dayjs (dayjs)
### [`v1.11.13`](https://togithub.com/iamkun/dayjs/compare/v1.11.12...93c8fd0f807b8a8252f4cd65083bb1d6a49b90e7) [Compare Source](https://togithub.com/iamkun/dayjs/compare/v1.11.12...v1.11.13)evanw/esbuild (esbuild)
### [`v0.23.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0231) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.23.0...v0.23.1) - Allow using the `node:` import prefix with `es*` targets ([#3821](https://togithub.com/evanw/esbuild/issues/3821)) The [`node:` prefix on imports](https://nodejs.org/api/esm.html#node-imports) is an alternate way to import built-in node modules. For example, `import fs from "fs"` can also be written `import fs from "node:fs"`. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with `--target=node14` so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as `--target=node18,es2022` removes the `node:` prefix because none of the `es*` targets are known to support this feature. This release adds the support for the `node:` flag to esbuild's internal compatibility table for `es*` to allow you to use compound targets like this: ```js // Original code import fs from 'node:fs' fs.open // Old output (with --bundle --format=esm --platform=node --target=node18,es2022) import fs from "fs"; fs.open; // New output (with --bundle --format=esm --platform=node --target=node18,es2022) import fs from "node:fs"; fs.open; ``` - Fix a panic when using the CLI with invalid build flags if `--analyze` is present ([#3834](https://togithub.com/evanw/esbuild/issues/3834)) Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the `--analyze` flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how `--analyze` is implemented) to a null build object. The panic has been fixed in this release. - Fix incorrect location of certain error messages ([#3845](https://togithub.com/evanw/esbuild/issues/3845)) This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild. - Print comments before case clauses in switch statements ([#3838](https://togithub.com/evanw/esbuild/issues/3838)) With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification). - Fix a memory leak with `pluginData` ([#3825](https://togithub.com/evanw/esbuild/issues/3825)) With this release, the build context's internal `pluginData` cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return `pluginData` objects from `onResolve` and/or `onLoad` callbacks.nodejs/node (node)
### [`v20.17.0`](https://togithub.com/nodejs/node/compare/v20.16.0...v20.17.0) [Compare Source](https://togithub.com/nodejs/node/compare/v20.16.0...v20.17.0)Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.