chore(deps-dev): Bump the development-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the development-dependencies group with 3 updates in the /api/src directory: @types/aws-lambda, esbuild and eslint.

Updates @types/aws-lambda from 8.10.143 to 8.10.145

Commits

• See full diff in compare view

Updates esbuild from 0.23.0 to 0.23.1

Release notes

Sourced from esbuild's releases.

v0.23.1

• Allow using the node: import prefix with es* targets (#3821)

  The node: prefix on 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:

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

  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)

  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)

  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)

  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.

Changelog

Sourced from esbuild's changelog.

0.23.1

• Allow using the node: import prefix with es* targets (#3821)

  The node: prefix on 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:

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

  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)

  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)

  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)

  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.

Commits

• 3327274 publish 0.23.1 to npm
• 38e22ed add a warning/debug log message for #3867
• a15bb51 fix #3825: memory leak of pluginData values
• f6e6481 fix #3838: print comments before case clauses
• 9c13ae1 fix #3853: update go 1.22.4 => 1.22.5
• 78f89e4 fix #3845: some incorrect error message locations
• 892d2a7 fix #3834: cli sometimes panics with --analyze
• 360d472 fix a typo in the release notes
• e3f4e2d fix #3821: allow node: prefix with es* targets
• See full diff in compare view

Updates eslint from 9.9.0 to 9.9.1

Release notes

Sourced from eslint's releases.

v9.9.1

Bug Fixes

• 9bde90c fix: add logic to handle fixTypes in lintText() (#18736) (Amaresh S M)

Documentation

• 4840930 docs: Update README with version support and clean up content (#18804) (Nicholas C. Zakas)
• f61f40d docs: Update globals examples (#18805) (Nicholas C. Zakas)
• 241fcea docs: Use and define languages (#18795) (Nicholas C. Zakas)
• 5dbdd63 docs: eslint-plugin-markdown -> @​eslint/markdown (#18797) (Nicholas C. Zakas)
• c6c8ddd docs: update links to eslint-visitor-keys repo (#18796) (Francesco Trotta)
• f981d05 docs: Update README (GitHub Actions Bot)
• b516974 docs: update links to eslint/js repo (#18781) (Francesco Trotta)
• fb7a3f5 docs: update note for package managers (#18779) (Jay)

Chores

• b0c34d0 chore: upgrade to @​eslint/js@​9.9.1 (#18809) (Francesco Trotta)
• cd5a0da chore: package.json update for @​eslint/js release (Jenkins)
• e112642 refactor: Extract parsing logic from Linter (#18790) (Nicholas C. Zakas)
• 0f68a85 chore: use eslint-plugin-yml on yaml files only (#18801) (Milos Djermanovic)
• f8d1b3c chore: update dependencies for browser tests (#18794) (Christian Bromann)
• aed2624 chore: update dependency @​eslint/config-array to ^0.18.0 (#18788) (renovate[bot])
• 5c29128 chore: update dependency @​eslint/core to ^0.4.0 (#18789) (renovate[bot])
• 5d66fb2 chore: migrate linting workflow to use trunk check meta-linter (#18643) (Chris Clearwater)
• bf96855 chore: add ids to github issue templates (#18775) (Strek)

Changelog

Sourced from eslint's changelog.

v9.9.1 - August 23, 2024

• b0c34d0 chore: upgrade to @​eslint/js@​9.9.1 (#18809) (Francesco Trotta)
• cd5a0da chore: package.json update for @​eslint/js release (Jenkins)
• 4840930 docs: Update README with version support and clean up content (#18804) (Nicholas C. Zakas)
• f61f40d docs: Update globals examples (#18805) (Nicholas C. Zakas)
• e112642 refactor: Extract parsing logic from Linter (#18790) (Nicholas C. Zakas)
• 241fcea docs: Use and define languages (#18795) (Nicholas C. Zakas)
• 0f68a85 chore: use eslint-plugin-yml on yaml files only (#18801) (Milos Djermanovic)
• 5dbdd63 docs: eslint-plugin-markdown -> @​eslint/markdown (#18797) (Nicholas C. Zakas)
• c6c8ddd docs: update links to eslint-visitor-keys repo (#18796) (Francesco Trotta)
• f8d1b3c chore: update dependencies for browser tests (#18794) (Christian Bromann)
• aed2624 chore: update dependency @​eslint/config-array to ^0.18.0 (#18788) (renovate[bot])
• 5c29128 chore: update dependency @​eslint/core to ^0.4.0 (#18789) (renovate[bot])
• 5d66fb2 chore: migrate linting workflow to use trunk check meta-linter (#18643) (Chris Clearwater)
• f981d05 docs: Update README (GitHub Actions Bot)
• b516974 docs: update links to eslint/js repo (#18781) (Francesco Trotta)
• fb7a3f5 docs: update note for package managers (#18779) (Jay)
• bf96855 chore: add ids to github issue templates (#18775) (Strek)
• 9bde90c fix: add logic to handle fixTypes in lintText() (#18736) (Amaresh S M)

Commits

• 8781e6f 9.9.1
• 1503d03 Build: changelog update for 9.9.1
• b0c34d0 chore: upgrade to @​eslint/js@​9.9.1 (#18809)
• cd5a0da chore: package.json update for @​eslint/js release
• 4840930 docs: Update README with version support and clean up content (#18804)
• f61f40d docs: Update globals examples (#18805)
• e112642 refactor: Extract parsing logic from Linter (#18790)
• 241fcea docs: Use and define languages (#18795)
• 0f68a85 chore: use eslint-plugin-yml on yaml files only (#18801)
• 5dbdd63 docs: eslint-plugin-markdown -> @​eslint/markdown (#18797)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Superseded by #61.