fix(deps): update all non-major dependencies #327

renovate · 2023-10-21T05:13:58Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@aws-sdk/client-lambda (source)	`3.433.0` -> `3.441.0`
@aws-sdk/client-sqs (source)	`3.433.0` -> `3.441.0`
@types/aws-lambda (source)	`8.10.119` -> `8.10.125`
@types/node (source)	`20.8.9` -> `20.8.10`
archiver	`6.0.0` -> `6.0.1`
dynamoose (source)	`3.2.0` -> `3.2.1`
esbuild	`0.19.2` -> `0.19.5`
esbuild-node-externals	`1.8.0` -> `1.9.0`
rimraf	`5.0.1` -> `5.0.5`
serverless (source)	`3.34.0` -> `3.36.0`
typescript (source)	`5.1.6` -> `5.2.2`

Release Notes

aws/aws-sdk-js-v3 (@aws-sdk/client-lambda)

`v3.441.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-lambda

`v3.438.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-lambda

`v3.437.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-lambda

`v3.436.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-lambda

`v3.435.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-lambda

aws/aws-sdk-js-v3 (@aws-sdk/client-sqs)

`v3.441.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-sqs

`v3.438.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-sqs

`v3.437.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-sqs

`v3.436.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-sqs

`v3.435.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-sqs

archiverjs/node-archiver (archiver)

`v6.0.1`

Compare Source

What’s changed

Maintenance

chore(deps): update actions/checkout action to v3.6.0 @renovate (#697)

Dependency updates

fix(deps): update dependency tar-stream to v3 @renovate (#691)
chore(deps): update actions/checkout action to v3.6.0 @renovate (#697)
chore(deps): update dependency chai to v4.3.8 @renovate (#696)
fix(deps): update dependency archiver-utils to v3.0.4 @renovate (#698)
fix(deps): update dependency zip-stream to v4.1.1 @renovate (#700)
chore(deps): lock file maintenance @renovate (#686)
fix(deps): update dependency archiver-utils to v4 @renovate (#701)
Update dependency archiver-utils to v4.0.1 @renovate (#705)
Update dependency zip-stream to v5 @renovate (#702)
Update dependency zip-stream to v5.0.1 @renovate (#706)

dynamoose/dynamoose (dynamoose)

`v3.2.1`

Compare Source

This release includes some minor bug fixes.

Please comment or contact me 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.5`

Compare Source

Fix a regression in 0.19.0 regarding paths in tsconfig.json (#3354)

The fix in esbuild version 0.19.0 to process tsconfig.json aliases before the --packages=external setting unintentionally broke an edge case in esbuild's handling of certain tsconfig.json aliases where there are multiple files with the same name in different directories. This release adjusts esbuild's behavior for this edge case so that it passes while still processing aliases before --packages=external. Please read the linked issue for more details.
Fix a CSS font property minification bug (#3452)

This release fixes a bug where esbuild's CSS minifier didn't insert a space between the font size and the font family in the font CSS shorthand property in the edge case where the original source code didn't already have a space and the leading string token was shortened to an identifier:
```
/* Original code */
.foo { font: 16px"Menlo"; }

/* Old output (with --minify) */
.foo{font:16pxMenlo}

/* New output (with --minify) */
.foo{font:16px Menlo}
```
Fix bundling CSS with asset names containing spaces (#3410)

Assets referenced via CSS url() tokens may cause esbuild to generate invalid output when bundling if the file name contains spaces (e.g. url(image 2.png)). With this release, esbuild will now quote all bundled asset references in url() tokens to avoid this problem. This only affects assets loaded using the file and copy loaders.
Fix invalid CSS url() tokens in @import rules (#3426)

In the future, CSS url() tokens may contain additional stuff after the URL. This is irrelevant today as no CSS specification does this. But esbuild previously had a bug where using these tokens in an @import rule resulted in malformed output. This bug has been fixed.
Fix browser + false + type: module in package.json (#3367)

The browser field in package.json allows you to map a file to false to have it be treated as an empty file when bundling for the browser. However, if package.json contains "type": "module" then all .js files will be considered ESM, not CommonJS. Importing a named import from an empty CommonJS file gives you undefined, but importing a named export from an empty ESM file is a build error. This release changes esbuild's interpretation of these files mapped to false in this situation from ESM to CommonJS to avoid generating build errors for named imports.
Fix a bug in top-level await error reporting (#3400)

Using require() on a file that contains top-level await is not allowed because require() must return synchronously and top-level await makes that impossible. You will get a build error if you try to bundle code that does this with esbuild. This release fixes a bug in esbuild's error reporting code for complex cases of this situation involving multiple levels of imports to get to the module containing the top-level await.
Update to Unicode 15.1.0

The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 15.0.0 to the newly-released Unicode version 15.1.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read https://www.unicode.org/versions/Unicode15.1.0/#Summary for more information about the changes.

This upgrade was contributed by @JLHwung.

`v0.19.4`

Compare Source

Fix printing of JavaScript decorators in tricky cases (#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:

// Original code
import { constant } from './constants.js'
import { imported } from 'external'
import { undef } from './empty.js'
class Foo {
  @&#8203;constant()
  @&#8203;imported()
  @&#8203;undef()
  foo
}

// Old output (with --bundle --format=cjs --packages=external --minify-syntax)
var import_external = require("external");
var Foo = class {
  @&#8203;123()
  @&#8203;(0, import_external.imported)()
  @&#8203;(void 0)()
  foo;
};

// New output (with --bundle --format=cjs --packages=external --minify-syntax)
var import_external = require("external");
var Foo = class {
  @&#8203;(123())
  @&#8203;((0, import_external.imported)())
  @&#8203;((void 0)())
  foo;
};

Allow pre-release versions to be passed to target (#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`

Compare Source

Fix list-style-type with the local-css loader (#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:
```
/* 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)

This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before use strict directives:

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

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:
```
// 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:
```
// 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)

This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example:

/* Original code */
@&#8203;KeyFrames Foo { From { OpaCity: 0 } To { OpaCity: 1 } }
body { CoLoR: YeLLoW }

/* Old output (with --minify) */
@&#8203;KeyFrames Foo{From {OpaCity: 0} To {OpaCity: 1}}body{CoLoR:YeLLoW}

/* New output (with --minify) */
@&#8203;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)

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:
```
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 is to add a feature called "import attributes" instead that adds a with keyword to import statements. It looks like this:
```
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`: esbuild-node-externals v1.9.0

Compare Source

Features

allow esbuild 0.19 (#46) (325b726)

isaacs/rimraf (rimraf)

serverless/serverless (serverless)

`v3.36.0`

Compare Source

Features

Improved dashboard documentation and gitignore (#12176) (eb462ed)

Bug Fixes

Dashboard documentation improvements (bb4d7c8)
Fix menu for dashboard documentation (8f266af)
Improve dashboard documentation (ad8bbf1)
Improve dashboard documentation (f67df7f)
Minor dashboard doc improvements (#12177) (f1fa19c)

3.35.2 (2023-09-16)

Bug Fixes

Adjust copy for clarity (#12162) (101ce53)

3.35.1 (2023-09-16)

Bug Fixes

Do not use isDashboard in onboarding flow (#12160) (1f8d786)

`v3.35.2`

Compare Source

`v3.35.1`

Compare Source

`v3.35.0`

Compare Source

Features

Make dashboard monitoring opt-out (#12138) (45cbd52)
Post deploy serverless dashboard integration (#12063) (66e3107), closes #12059
Remove Console Login (#12153) (590bb7e)
Remove Dashboard onboarding from framework (#12151) (6ee277d)
Upgrade to @serverless/dashboard-plugin (#12157) (f057629)

Bug Fixes

Adjust providers endpoint (#12154) (9b770a2), closes #12151
Check for Serverless Dashboard IAM stack prior to creation (#12147) (bf518b9)
Handle account being integrated with an existing org (#12149) (561a875)
Local credentials should be resolved in onboarding command (#12148) (307865d)
recognize ap-south-2 as a valid AWS region (#12129) (b09d0d6)

3.34.0 (2023-08-03)

Features

Python 3.11 support (#12085) (f5d143a)

Bug Fixes

AWS Schedule: Fix IAM role assignment (#12030) (e1039de)

Maintenance Improvements

Remove got dependency (#12040) (1775c90)

Microsoft/TypeScript (typescript)

`v5.2.2`: TypeScript 5.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

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.

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from dbfe1f0 to f3c5331 Compare October 24, 2023 20:29

renovate bot changed the title ~~chore(deps): update all non-major dependencies~~ fix(deps): update all non-major dependencies Oct 24, 2023

renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 2e14e1f to e4fea05 Compare October 31, 2023 11:13

renovate bot force-pushed the renovate/all-minor-patch branch from e4fea05 to 7b09534 Compare November 1, 2023 22:31

fix(deps): update all non-major dependencies

e8d2ed5

renovate bot force-pushed the renovate/all-minor-patch branch from 7b09534 to e8d2ed5 Compare November 6, 2023 06:17

renovate bot merged commit b788da0 into main Nov 6, 2023
30 checks passed

renovate bot deleted the renovate/all-minor-patch branch November 6, 2023 11:40

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update all non-major dependencies #327

fix(deps): update all non-major dependencies #327

renovate bot commented Oct 21, 2023 •

edited

Loading

fix(deps): update all non-major dependencies #327

fix(deps): update all non-major dependencies #327

Conversation

renovate bot commented Oct 21, 2023 • edited Loading

Release Notes

What’s changed

Maintenance

Dependency updates

Bug Fixes

Documentation

v1.9.0: esbuild-node-externals v1.9.0

Features

Features

Bug Fixes

3.35.2 (2023-09-16)

Bug Fixes

3.35.1 (2023-09-16)

Bug Fixes

Features

Bug Fixes

3.34.0 (2023-08-03)

Features

Bug Fixes

Maintenance Improvements

v5.2.2: TypeScript 5.2

Configuration

renovate bot commented Oct 21, 2023 •

edited

Loading

`v1.9.0`: esbuild-node-externals v1.9.0

`v5.2.2`: TypeScript 5.2