aws/aws-sdk-js-v3 (@aws-sdk/client-lambda)
### [`v3.428.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-lambda/CHANGELOG.md#34280-2023-10-12)
[Compare Source](https://togithub.com/aws/aws-sdk-js-v3/compare/v3.427.0...v3.428.0)
##### Features
- **client-lambda:** Adds support for Lambda functions to access Dual-Stack subnets over IPv6, via an opt-in flag in CreateFunction and UpdateFunctionConfiguration APIs ([2bb63a0](https://togithub.com/aws/aws-sdk-js-v3/commit/2bb63a023100d2133b8050c1eb528f04444bd576))
aws/aws-sdk-js-v3 (@aws-sdk/client-sqs)
### [`v3.428.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-sqs/CHANGELOG.md#34280-2023-10-12)
[Compare Source](https://togithub.com/aws/aws-sdk-js-v3/compare/v3.427.0...v3.428.0)
**Note:** Version bump only for package [@aws-sdk/client-sqs](https://togithub.com/aws-sdk/client-sqs)
archiverjs/node-archiver (archiver)
### [`v6.0.1`](https://togithub.com/archiverjs/node-archiver/releases/tag/6.0.1)
[Compare Source](https://togithub.com/archiverjs/node-archiver/compare/6.0.0...6.0.1)
#### What’s changed
#### Maintenance
- chore(deps): update actions/checkout action to v3.6.0 [@renovate](https://togithub.com/renovate) ([#697](https://togithub.com/archiverjs/node-archiver/issues/697))
#### Dependency updates
- fix(deps): update dependency tar-stream to v3 [@renovate](https://togithub.com/renovate) ([#691](https://togithub.com/archiverjs/node-archiver/issues/691))
- chore(deps): update actions/checkout action to v3.6.0 [@renovate](https://togithub.com/renovate) ([#697](https://togithub.com/archiverjs/node-archiver/issues/697))
- chore(deps): update dependency chai to v4.3.8 [@renovate](https://togithub.com/renovate) ([#696](https://togithub.com/archiverjs/node-archiver/issues/696))
- fix(deps): update dependency archiver-utils to v3.0.4 [@renovate](https://togithub.com/renovate) ([#698](https://togithub.com/archiverjs/node-archiver/issues/698))
- fix(deps): update dependency zip-stream to v4.1.1 [@renovate](https://togithub.com/renovate) ([#700](https://togithub.com/archiverjs/node-archiver/issues/700))
- chore(deps): lock file maintenance [@renovate](https://togithub.com/renovate) ([#686](https://togithub.com/archiverjs/node-archiver/issues/686))
- fix(deps): update dependency archiver-utils to v4 [@renovate](https://togithub.com/renovate) ([#701](https://togithub.com/archiverjs/node-archiver/issues/701))
- Update dependency archiver-utils to v4.0.1 [@renovate](https://togithub.com/renovate) ([#705](https://togithub.com/archiverjs/node-archiver/issues/705))
- Update dependency zip-stream to v5 [@renovate](https://togithub.com/renovate) ([#702](https://togithub.com/archiverjs/node-archiver/issues/702))
- Update dependency zip-stream to v5.0.1 [@renovate](https://togithub.com/renovate) ([#706](https://togithub.com/archiverjs/node-archiver/issues/706))
dynamoose/dynamoose (dynamoose)
### [`v3.2.1`](https://togithub.com/dynamoose/dynamoose/blob/HEAD/CHANGELOG.md#Version-321)
[Compare Source](https://togithub.com/dynamoose/dynamoose/compare/v3.2.0...v3.2.1)
This release includes some minor bug fixes.
Please comment or [contact me](https://charlie.fish/contact) if you have any questions about this release.
##### Bug Fixes
- Fixes inputs types for Mode.update(), allowing $SET, $ADD, $DELETE and $REMOVE
- Fixes save bug with expires set to object with no ttl
##### Documentation
- Grammar fixes
- Fixing Mastodon verification link
***
evanw/esbuild (esbuild)
### [`v0.19.4`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0194)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.3...v0.19.4)
- Fix printing of JavaScript decorators in tricky cases ([#3396](https://togithub.com/evanw/esbuild/issues/3396))
This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples:
```js
// Original code
import { constant } from './constants.js'
import { imported } from 'external'
import { undef } from './empty.js'
class Foo {
@constant()
@imported()
@undef()
foo
}
// Old output (with --bundle --format=cjs --packages=external --minify-syntax)
var import_external = require("external");
var Foo = class {
@123()
@(0, import_external.imported)()
@(void 0)()
foo;
};
// New output (with --bundle --format=cjs --packages=external --minify-syntax)
var import_external = require("external");
var Foo = class {
@(123())
@((0, import_external.imported)())
@((void 0)())
foo;
};
```
- Allow pre-release versions to be passed to `target` ([#3388](https://togithub.com/evanw/esbuild/issues/3388))
People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's `target` setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed to `target` and do something reasonable with them.
### [`v0.19.3`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0193)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.2...v0.19.3)
- Fix `list-style-type` with the `local-css` loader ([#3325](https://togithub.com/evanw/esbuild/issues/3325))
The `local-css` loader incorrectly treated all identifiers provided to `list-style-type` as a custom local identifier. That included identifiers such as `none` which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:
```css
/* Original code */
ul { list-style-type: none }
/* Old output (with --loader=local-css) */
ul {
list-style-type: stdin_none;
}
/* New output (with --loader=local-css) */
ul {
list-style-type: none;
}
```
Note that this bug only affected code using the `local-css` loader. It did not affect code using the `css` loader.
- Avoid inserting temporary variables before `use strict` ([#3322](https://togithub.com/evanw/esbuild/issues/3322))
This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before `use strict` directives:
```js
// Original code
function foo() {
'use strict'
a.b?.c()
}
// Old output (with --target=es6)
function foo() {
var _a;
"use strict";
(_a = a.b) == null ? void 0 : _a.c();
}
// New output (with --target=es6)
function foo() {
"use strict";
var _a;
(_a = a.b) == null ? void 0 : _a.c();
}
```
- Adjust TypeScript `enum` output to better approximate `tsc` ([#3329](https://togithub.com/evanw/esbuild/issues/3329))
TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number:
```ts
// Original TypeScript code
declare const foo: any
enum Foo {
NUMBER = 1,
STRING = 'a',
OTHER = foo,
}
// Compiled JavaScript code (from "tsc")
var Foo;
(function (Foo) {
Foo[Foo["NUMBER"] = 1] = "NUMBER";
Foo["STRING"] = "a";
Foo[Foo["OTHER"] = foo] = "OTHER";
})(Foo || (Foo = {}));
```
However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases:
```ts
// Original TypeScript code
declare const foo = 'foo'
enum Foo {
PRESENT = `${foo}`,
MISSING = `${bar}`,
}
// Compiled JavaScript code (from "tsc")
var Foo;
(function (Foo) {
Foo["PRESENT"] = "foo";
Foo[Foo["MISSING"] = `${bar}`] = "MISSING";
})(Foo || (Foo = {}));
```
The template literal initializer for `PRESENT` is treated as a string while the template literal initializer for `MISSING` is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior of `tsc` but in the case where the behavior diverges `tsc` reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see the `declare` keyword), which esbuild deliberately doesn't do.
- Ignore case in CSS in more places ([#3316](https://togithub.com/evanw/esbuild/issues/3316))
This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example:
```css
/* Original code */
@KeyFrames Foo { From { OpaCity: 0 } To { OpaCity: 1 } }
body { CoLoR: YeLLoW }
/* Old output (with --minify) */
@KeyFrames Foo{From {OpaCity: 0} To {OpaCity: 1}}body{CoLoR:YeLLoW}
/* New output (with --minify) */
@KeyFrames Foo{0%{OpaCity:0}To{OpaCity:1}}body{CoLoR:#ff0}
```
Please never actually write code like this.
- Improve the error message for `null` entries in `exports` ([#3377](https://togithub.com/evanw/esbuild/issues/3377))
Package authors can disable package export paths with the `exports` map in `package.json`. With this release, esbuild now has a clearer error message that points to the `null` token in `package.json` itself instead of to the surrounding context. Here is an example of the new error message:
✘ [ERROR] Could not resolve "msw/browser"
lib/msw-config.ts:2:28:
2 │ import { setupWorker } from 'msw/browser';
╵ ~~~~~~~~~~~~~
The path "./browser" cannot be imported from package "msw" because it was explicitly disabled by
the package author here:
node_modules/msw/package.json:17:14:
17 │ "node": null,
╵ ~~~~
You can mark the path "msw/browser" as external to exclude it from the bundle, which will remove
this error and leave the unresolved path in the bundle.
- Parse and print the `with` keyword in `import` statements
JavaScript was going to have a feature called "import assertions" that adds an `assert` keyword to `import` statements. It looked like this:
```js
import stuff from './stuff.json' assert { type: 'json' }
```
The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language.
Instead, the [current proposal](https://togithub.com/tc39/proposal-import-attributes) is to add a feature called "import attributes" instead that adds a `with` keyword to import statements. It looks like this:
```js
import stuff from './stuff.json' with { type: 'json' }
```
This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new `with` keyword. The `with` keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too.
pradel/esbuild-node-externals (esbuild-node-externals)
### [`v1.9.0`](https://togithub.com/pradel/esbuild-node-externals/releases/tag/v1.9.0): esbuild-node-externals v1.9.0
[Compare Source](https://togithub.com/pradel/esbuild-node-externals/compare/v1.8.0...v1.9.0)
##### Features
- allow esbuild 0.19 ([#46](https://www.togithub.com/pradel/esbuild-node-externals/issues/46)) ([325b726](https://www.github.com/pradel/esbuild-node-externals/commit/325b726022720d98e7e60393fb79a645134070c4))
isaacs/rimraf (rimraf)
### [`v5.0.5`](https://togithub.com/isaacs/rimraf/compare/v5.0.4...v5.0.5)
[Compare Source](https://togithub.com/isaacs/rimraf/compare/v5.0.4...v5.0.5)
### [`v5.0.4`](https://togithub.com/isaacs/rimraf/compare/v5.0.3...v5.0.4)
[Compare Source](https://togithub.com/isaacs/rimraf/compare/v5.0.3...v5.0.4)
### [`v5.0.3`](https://togithub.com/isaacs/rimraf/compare/v5.0.2...v5.0.3)
[Compare Source](https://togithub.com/isaacs/rimraf/compare/v5.0.2...v5.0.3)
### [`v5.0.2`](https://togithub.com/isaacs/rimraf/compare/v5.0.1...v5.0.2)
[Compare Source](https://togithub.com/isaacs/rimraf/compare/v5.0.1...v5.0.2)
serverless/serverless (serverless)
### [`v3.35.2`](https://togithub.com/serverless/serverless/blob/HEAD/CHANGELOG.md#3352-2023-09-16)
[Compare Source](https://togithub.com/serverless/serverless/compare/v3.35.1...v3.35.2)
### [`v3.35.1`](https://togithub.com/serverless/serverless/blob/HEAD/CHANGELOG.md#3351-2023-09-16)
[Compare Source](https://togithub.com/serverless/serverless/compare/v3.35.0...v3.35.1)
### [`v3.35.0`](https://togithub.com/serverless/serverless/blob/HEAD/CHANGELOG.md#3350-2023-09-15)
[Compare Source](https://togithub.com/serverless/serverless/compare/v3.34.0...v3.35.0)
##### Features
- Make dashboard monitoring opt-out ([#12138](https://togithub.com/serverless/serverless/issues/12138)) ([45cbd52](https://togithub.com/serverless/serverless/commit/45cbd525014ad3bf60aac3d482ec76ce68b51820))
- Post deploy serverless dashboard integration ([#12063](https://togithub.com/serverless/serverless/issues/12063)) ([66e3107](https://togithub.com/serverless/serverless/commit/66e31077a71c61854db3246a50ddd2c1c303c110)), closes [#12059](https://togithub.com/serverless/serverless/issues/12059)
- Remove Console Login ([#12153](https://togithub.com/serverless/serverless/issues/12153)) ([590bb7e](https://togithub.com/serverless/serverless/commit/590bb7e17717253bfa37b1b511e5a6610c5657cb))
- Remove Dashboard onboarding from framework ([#12151](https://togithub.com/serverless/serverless/issues/12151)) ([6ee277d](https://togithub.com/serverless/serverless/commit/6ee277dfcb0d9055a3b20cbf493b1fd79b524fd2))
- Upgrade to [@serverless/dashboard-plugin](https://togithub.com/serverless/dashboard-plugin) ([#12157](https://togithub.com/serverless/serverless/issues/12157)) ([f057629](https://togithub.com/serverless/serverless/commit/f057629cbebf07f3415ef996ecbc10c7c7b866d4))
##### Bug Fixes
- Adjust providers endpoint ([#12154](https://togithub.com/serverless/serverless/issues/12154)) ([9b770a2](https://togithub.com/serverless/serverless/commit/9b770a27dc0a093d05d36e58f077b3a527565718)), closes [#12151](https://togithub.com/serverless/serverless/issues/12151)
- Check for Serverless Dashboard IAM stack prior to creation ([#12147](https://togithub.com/serverless/serverless/issues/12147)) ([bf518b9](https://togithub.com/serverless/serverless/commit/bf518b9135997c67ea940ff396af14a4b4b62948))
- Handle account being integrated with an existing org ([#12149](https://togithub.com/serverless/serverless/issues/12149)) ([561a875](https://togithub.com/serverless/serverless/commit/561a875da767a23e6bc1cc314e726ff674ab9df1))
- Local credentials should be resolved in onboarding command ([#12148](https://togithub.com/serverless/serverless/issues/12148)) ([307865d](https://togithub.com/serverless/serverless/commit/307865d0525d551f188a1c86399533f78d7b15c3))
- recognize ap-south-2 as a valid AWS region ([#12129](https://togithub.com/serverless/serverless/issues/12129)) ([b09d0d6](https://togithub.com/serverless/serverless/commit/b09d0d62677c09c4905b65bcaf6ba61aa8d8204c))
##### [3.34.0](https://togithub.com/serverless/serverless/compare/v3.33.0...v3.34.0) (2023-08-03)
##### Features
- Python 3.11 support ([#12085](https://togithub.com/serverless/serverless/issues/12085)) ([f5d143a](https://togithub.com/serverless/serverless/commit/f5d143ac3935260dc0f647a541f22dbbd583095f))
##### Bug Fixes
- **AWS Schedule:** Fix IAM role assignment ([#12030](https://togithub.com/serverless/serverless/issues/12030)) ([e1039de](https://togithub.com/serverless/serverless/commit/e1039ded5c5e35595b5d4c59e81d480a16c4dd67))
##### Maintenance Improvements
- Remove `got` dependency ([#12040](https://togithub.com/serverless/serverless/issues/12040)) ([1775c90](https://togithub.com/serverless/serverless/commit/1775c90a72ec321af8673bcdd1901cb1e48b9169))
Microsoft/TypeScript (typescript)
### [`v5.2.2`](https://togithub.com/microsoft/TypeScript/releases/tag/v5.2.2): TypeScript 5.2
[Compare Source](https://togithub.com/Microsoft/TypeScript/compare/v5.1.6...v5.2.2)
For release notes, check out the [release announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/).
For the complete list of fixed issues, check out the
- [fixed issues query for Typescript 5.2.0 (Beta)](https://togithub.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.2.0%22+is%3Aclosed+).
- [fixed issues query for Typescript 5.2.1 (RC)](https://togithub.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.2.1%22+is%3Aclosed+).
- [fixed issues query for Typescript 5.2.2 (Stable)](https://togithub.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.2.2%22+is%3Aclosed+).
Downloads are available on:
- [NuGet package](https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR contains the following updates:
3.427.0
->3.428.0
3.427.0
->3.428.0
5.3.2
->5.3.3
8.10.119
->8.10.124
18.17.9
->18.18.5
6.0.0
->6.0.1
3.2.0
->3.2.1
0.19.2
->0.19.4
1.8.0
->1.9.0
5.0.1
->5.0.5
3.34.0
->3.35.2
5.1.6
->5.2.2
Release Notes
aws/aws-sdk-js-v3 (@aws-sdk/client-lambda)
### [`v3.428.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-lambda/CHANGELOG.md#34280-2023-10-12) [Compare Source](https://togithub.com/aws/aws-sdk-js-v3/compare/v3.427.0...v3.428.0) ##### Features - **client-lambda:** Adds support for Lambda functions to access Dual-Stack subnets over IPv6, via an opt-in flag in CreateFunction and UpdateFunctionConfiguration APIs ([2bb63a0](https://togithub.com/aws/aws-sdk-js-v3/commit/2bb63a023100d2133b8050c1eb528f04444bd576))aws/aws-sdk-js-v3 (@aws-sdk/client-sqs)
### [`v3.428.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-sqs/CHANGELOG.md#34280-2023-10-12) [Compare Source](https://togithub.com/aws/aws-sdk-js-v3/compare/v3.427.0...v3.428.0) **Note:** Version bump only for package [@aws-sdk/client-sqs](https://togithub.com/aws-sdk/client-sqs)archiverjs/node-archiver (archiver)
### [`v6.0.1`](https://togithub.com/archiverjs/node-archiver/releases/tag/6.0.1) [Compare Source](https://togithub.com/archiverjs/node-archiver/compare/6.0.0...6.0.1) #### What’s changed #### Maintenance - chore(deps): update actions/checkout action to v3.6.0 [@renovate](https://togithub.com/renovate) ([#697](https://togithub.com/archiverjs/node-archiver/issues/697)) #### Dependency updates - fix(deps): update dependency tar-stream to v3 [@renovate](https://togithub.com/renovate) ([#691](https://togithub.com/archiverjs/node-archiver/issues/691)) - chore(deps): update actions/checkout action to v3.6.0 [@renovate](https://togithub.com/renovate) ([#697](https://togithub.com/archiverjs/node-archiver/issues/697)) - chore(deps): update dependency chai to v4.3.8 [@renovate](https://togithub.com/renovate) ([#696](https://togithub.com/archiverjs/node-archiver/issues/696)) - fix(deps): update dependency archiver-utils to v3.0.4 [@renovate](https://togithub.com/renovate) ([#698](https://togithub.com/archiverjs/node-archiver/issues/698)) - fix(deps): update dependency zip-stream to v4.1.1 [@renovate](https://togithub.com/renovate) ([#700](https://togithub.com/archiverjs/node-archiver/issues/700)) - chore(deps): lock file maintenance [@renovate](https://togithub.com/renovate) ([#686](https://togithub.com/archiverjs/node-archiver/issues/686)) - fix(deps): update dependency archiver-utils to v4 [@renovate](https://togithub.com/renovate) ([#701](https://togithub.com/archiverjs/node-archiver/issues/701)) - Update dependency archiver-utils to v4.0.1 [@renovate](https://togithub.com/renovate) ([#705](https://togithub.com/archiverjs/node-archiver/issues/705)) - Update dependency zip-stream to v5 [@renovate](https://togithub.com/renovate) ([#702](https://togithub.com/archiverjs/node-archiver/issues/702)) - Update dependency zip-stream to v5.0.1 [@renovate](https://togithub.com/renovate) ([#706](https://togithub.com/archiverjs/node-archiver/issues/706))dynamoose/dynamoose (dynamoose)
### [`v3.2.1`](https://togithub.com/dynamoose/dynamoose/blob/HEAD/CHANGELOG.md#Version-321) [Compare Source](https://togithub.com/dynamoose/dynamoose/compare/v3.2.0...v3.2.1) This release includes some minor bug fixes. Please comment or [contact me](https://charlie.fish/contact) if you have any questions about this release. ##### Bug Fixes - Fixes inputs types for Mode.update(), allowing $SET, $ADD, $DELETE and $REMOVE - Fixes save bug with expires set to object with no ttl ##### Documentation - Grammar fixes - Fixing Mastodon verification link ***evanw/esbuild (esbuild)
### [`v0.19.4`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0194) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.3...v0.19.4) - Fix printing of JavaScript decorators in tricky cases ([#3396](https://togithub.com/evanw/esbuild/issues/3396)) This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples: ```js // Original code import { constant } from './constants.js' import { imported } from 'external' import { undef } from './empty.js' class Foo { @constant() @imported() @undef() foo } // Old output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { @123() @(0, import_external.imported)() @(void 0)() foo; }; // New output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { @(123()) @((0, import_external.imported)()) @((void 0)()) foo; }; ``` - Allow pre-release versions to be passed to `target` ([#3388](https://togithub.com/evanw/esbuild/issues/3388)) People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's `target` setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed to `target` and do something reasonable with them. ### [`v0.19.3`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0193) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.2...v0.19.3) - Fix `list-style-type` with the `local-css` loader ([#3325](https://togithub.com/evanw/esbuild/issues/3325)) The `local-css` loader incorrectly treated all identifiers provided to `list-style-type` as a custom local identifier. That included identifiers such as `none` which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug: ```css /* Original code */ ul { list-style-type: none } /* Old output (with --loader=local-css) */ ul { list-style-type: stdin_none; } /* New output (with --loader=local-css) */ ul { list-style-type: none; } ``` Note that this bug only affected code using the `local-css` loader. It did not affect code using the `css` loader. - Avoid inserting temporary variables before `use strict` ([#3322](https://togithub.com/evanw/esbuild/issues/3322)) This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before `use strict` directives: ```js // Original code function foo() { 'use strict' a.b?.c() } // Old output (with --target=es6) function foo() { var _a; "use strict"; (_a = a.b) == null ? void 0 : _a.c(); } // New output (with --target=es6) function foo() { "use strict"; var _a; (_a = a.b) == null ? void 0 : _a.c(); } ``` - Adjust TypeScript `enum` output to better approximate `tsc` ([#3329](https://togithub.com/evanw/esbuild/issues/3329)) TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number: ```ts // Original TypeScript code declare const foo: any enum Foo { NUMBER = 1, STRING = 'a', OTHER = foo, } // Compiled JavaScript code (from "tsc") var Foo; (function (Foo) { Foo[Foo["NUMBER"] = 1] = "NUMBER"; Foo["STRING"] = "a"; Foo[Foo["OTHER"] = foo] = "OTHER"; })(Foo || (Foo = {})); ``` However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases: ```ts // Original TypeScript code declare const foo = 'foo' enum Foo { PRESENT = `${foo}`, MISSING = `${bar}`, } // Compiled JavaScript code (from "tsc") var Foo; (function (Foo) { Foo["PRESENT"] = "foo"; Foo[Foo["MISSING"] = `${bar}`] = "MISSING"; })(Foo || (Foo = {})); ``` The template literal initializer for `PRESENT` is treated as a string while the template literal initializer for `MISSING` is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior of `tsc` but in the case where the behavior diverges `tsc` reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see the `declare` keyword), which esbuild deliberately doesn't do. - Ignore case in CSS in more places ([#3316](https://togithub.com/evanw/esbuild/issues/3316)) This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example: ```css /* Original code */ @KeyFrames Foo { From { OpaCity: 0 } To { OpaCity: 1 } } body { CoLoR: YeLLoW } /* Old output (with --minify) */ @KeyFrames Foo{From {OpaCity: 0} To {OpaCity: 1}}body{CoLoR:YeLLoW} /* New output (with --minify) */ @KeyFrames Foo{0%{OpaCity:0}To{OpaCity:1}}body{CoLoR:#ff0} ``` Please never actually write code like this. - Improve the error message for `null` entries in `exports` ([#3377](https://togithub.com/evanw/esbuild/issues/3377)) Package authors can disable package export paths with the `exports` map in `package.json`. With this release, esbuild now has a clearer error message that points to the `null` token in `package.json` itself instead of to the surrounding context. Here is an example of the new error message: ✘ [ERROR] Could not resolve "msw/browser" lib/msw-config.ts:2:28: 2 │ import { setupWorker } from 'msw/browser'; ╵ ~~~~~~~~~~~~~ The path "./browser" cannot be imported from package "msw" because it was explicitly disabled by the package author here: node_modules/msw/package.json:17:14: 17 │ "node": null, ╵ ~~~~ You can mark the path "msw/browser" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. - Parse and print the `with` keyword in `import` statements JavaScript was going to have a feature called "import assertions" that adds an `assert` keyword to `import` statements. It looked like this: ```js import stuff from './stuff.json' assert { type: 'json' } ``` The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language. Instead, the [current proposal](https://togithub.com/tc39/proposal-import-attributes) is to add a feature called "import attributes" instead that adds a `with` keyword to import statements. It looks like this: ```js import stuff from './stuff.json' with { type: 'json' } ``` This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new `with` keyword. The `with` keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too.pradel/esbuild-node-externals (esbuild-node-externals)
### [`v1.9.0`](https://togithub.com/pradel/esbuild-node-externals/releases/tag/v1.9.0): esbuild-node-externals v1.9.0 [Compare Source](https://togithub.com/pradel/esbuild-node-externals/compare/v1.8.0...v1.9.0) ##### Features - allow esbuild 0.19 ([#46](https://www.togithub.com/pradel/esbuild-node-externals/issues/46)) ([325b726](https://www.github.com/pradel/esbuild-node-externals/commit/325b726022720d98e7e60393fb79a645134070c4))isaacs/rimraf (rimraf)
### [`v5.0.5`](https://togithub.com/isaacs/rimraf/compare/v5.0.4...v5.0.5) [Compare Source](https://togithub.com/isaacs/rimraf/compare/v5.0.4...v5.0.5) ### [`v5.0.4`](https://togithub.com/isaacs/rimraf/compare/v5.0.3...v5.0.4) [Compare Source](https://togithub.com/isaacs/rimraf/compare/v5.0.3...v5.0.4) ### [`v5.0.3`](https://togithub.com/isaacs/rimraf/compare/v5.0.2...v5.0.3) [Compare Source](https://togithub.com/isaacs/rimraf/compare/v5.0.2...v5.0.3) ### [`v5.0.2`](https://togithub.com/isaacs/rimraf/compare/v5.0.1...v5.0.2) [Compare Source](https://togithub.com/isaacs/rimraf/compare/v5.0.1...v5.0.2)serverless/serverless (serverless)
### [`v3.35.2`](https://togithub.com/serverless/serverless/blob/HEAD/CHANGELOG.md#3352-2023-09-16) [Compare Source](https://togithub.com/serverless/serverless/compare/v3.35.1...v3.35.2) ### [`v3.35.1`](https://togithub.com/serverless/serverless/blob/HEAD/CHANGELOG.md#3351-2023-09-16) [Compare Source](https://togithub.com/serverless/serverless/compare/v3.35.0...v3.35.1) ### [`v3.35.0`](https://togithub.com/serverless/serverless/blob/HEAD/CHANGELOG.md#3350-2023-09-15) [Compare Source](https://togithub.com/serverless/serverless/compare/v3.34.0...v3.35.0) ##### Features - Make dashboard monitoring opt-out ([#12138](https://togithub.com/serverless/serverless/issues/12138)) ([45cbd52](https://togithub.com/serverless/serverless/commit/45cbd525014ad3bf60aac3d482ec76ce68b51820)) - Post deploy serverless dashboard integration ([#12063](https://togithub.com/serverless/serverless/issues/12063)) ([66e3107](https://togithub.com/serverless/serverless/commit/66e31077a71c61854db3246a50ddd2c1c303c110)), closes [#12059](https://togithub.com/serverless/serverless/issues/12059) - Remove Console Login ([#12153](https://togithub.com/serverless/serverless/issues/12153)) ([590bb7e](https://togithub.com/serverless/serverless/commit/590bb7e17717253bfa37b1b511e5a6610c5657cb)) - Remove Dashboard onboarding from framework ([#12151](https://togithub.com/serverless/serverless/issues/12151)) ([6ee277d](https://togithub.com/serverless/serverless/commit/6ee277dfcb0d9055a3b20cbf493b1fd79b524fd2)) - Upgrade to [@serverless/dashboard-plugin](https://togithub.com/serverless/dashboard-plugin) ([#12157](https://togithub.com/serverless/serverless/issues/12157)) ([f057629](https://togithub.com/serverless/serverless/commit/f057629cbebf07f3415ef996ecbc10c7c7b866d4)) ##### Bug Fixes - Adjust providers endpoint ([#12154](https://togithub.com/serverless/serverless/issues/12154)) ([9b770a2](https://togithub.com/serverless/serverless/commit/9b770a27dc0a093d05d36e58f077b3a527565718)), closes [#12151](https://togithub.com/serverless/serverless/issues/12151) - Check for Serverless Dashboard IAM stack prior to creation ([#12147](https://togithub.com/serverless/serverless/issues/12147)) ([bf518b9](https://togithub.com/serverless/serverless/commit/bf518b9135997c67ea940ff396af14a4b4b62948)) - Handle account being integrated with an existing org ([#12149](https://togithub.com/serverless/serverless/issues/12149)) ([561a875](https://togithub.com/serverless/serverless/commit/561a875da767a23e6bc1cc314e726ff674ab9df1)) - Local credentials should be resolved in onboarding command ([#12148](https://togithub.com/serverless/serverless/issues/12148)) ([307865d](https://togithub.com/serverless/serverless/commit/307865d0525d551f188a1c86399533f78d7b15c3)) - recognize ap-south-2 as a valid AWS region ([#12129](https://togithub.com/serverless/serverless/issues/12129)) ([b09d0d6](https://togithub.com/serverless/serverless/commit/b09d0d62677c09c4905b65bcaf6ba61aa8d8204c)) ##### [3.34.0](https://togithub.com/serverless/serverless/compare/v3.33.0...v3.34.0) (2023-08-03) ##### Features - Python 3.11 support ([#12085](https://togithub.com/serverless/serverless/issues/12085)) ([f5d143a](https://togithub.com/serverless/serverless/commit/f5d143ac3935260dc0f647a541f22dbbd583095f)) ##### Bug Fixes - **AWS Schedule:** Fix IAM role assignment ([#12030](https://togithub.com/serverless/serverless/issues/12030)) ([e1039de](https://togithub.com/serverless/serverless/commit/e1039ded5c5e35595b5d4c59e81d480a16c4dd67)) ##### Maintenance Improvements - Remove `got` dependency ([#12040](https://togithub.com/serverless/serverless/issues/12040)) ([1775c90](https://togithub.com/serverless/serverless/commit/1775c90a72ec321af8673bcdd1901cb1e48b9169))Microsoft/TypeScript (typescript)
### [`v5.2.2`](https://togithub.com/microsoft/TypeScript/releases/tag/v5.2.2): TypeScript 5.2 [Compare Source](https://togithub.com/Microsoft/TypeScript/compare/v5.1.6...v5.2.2) For release notes, check out the [release announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/). For the complete list of fixed issues, check out the - [fixed issues query for Typescript 5.2.0 (Beta)](https://togithub.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.2.0%22+is%3Aclosed+). - [fixed issues query for Typescript 5.2.1 (RC)](https://togithub.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.2.1%22+is%3Aclosed+). - [fixed issues query for Typescript 5.2.2 (Stable)](https://togithub.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.2.2%22+is%3Aclosed+). Downloads are available on: - [NuGet package](https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.