fix(deps): ⬆️ update all non-major dependencies - autoclosed

[WolfSoko]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@analogjs/content (source)	1.5.0 -> 1.7.3
@analogjs/platform (source)	1.5.0 -> 1.7.3
@analogjs/router (source)	1.5.0 -> 1.7.3
@analogjs/vite-plugin-angular	1.5.0 -> 1.7.3
@analogjs/vite-plugin-nitro (source)	1.5.0 -> 1.7.3
@assemblyscript/loader (source)	0.27.27 -> 0.27.29
@esbuild/linux-x64	^0.21.5 -> ^0.23.1
@ngneat/effects-ng	^3.1.3 -> ^3.1.4
@rollup/rollup-linux-x64-gnu (source)	^4.18.0 -> ^4.21.2
@rollup/rollup-win32-x64-msvc (source)	^4.18.0 -> ^4.21.2
@tensorflow/tfjs	4.20.0 -> 4.21.0
ace-builds	1.35.0 -> 1.36.2
angulartics2 (source)	14.0.0 -> 14.1.0
aws-cdk (source)	^2.146.0 -> ^2.155.0
aws-cdk-lib (source)	^2.146.0 -> ^2.155.0
browserslist	4.23.1 -> 4.23.3
core-js (source)	3.37.1 -> 3.38.1
firebase (source, changelog)	10.12.2 -> 10.13.1
firebase-functions	^5.0.1 -> ^5.1.1
marked-gfm-heading-id	^4.0.0 -> ^4.1.0
marked-highlight	^2.1.3 -> ^2.1.4
marked-mangle	^1.1.8 -> ^1.1.9
mathjs (source)	13.0.0 -> 13.1.1
p5	1.9.4 -> 1.10.0
three (source)	0.165.0 -> 0.168.0
vega-embed	6.25.0 -> 6.26.0
vega-lite (source)	5.19.0 -> 5.21.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

analogjs/analog (@​analogjs/content)

v1.7.3

Compare Source

Bug Fixes

• content: initial support for running with Zoneless change detection (#​1284) (d5404c9)
• create-analog: add minimal template option (#​1293) (2af66fc)
• nx-plugin: remove fileReplacements from vite build schema (#​1306) (6d9c7c8)
• platform: prevent rxfire package from being externalized during SSR (#​1298) (89f63a4)
• trpc: support running with Zoneless change detection (#​1301) (fc7d50a)
• update templates to use vitest-angular import for testing (#​1292) (0587112)
• vite-plugin-angular: remove @​ngtools/webpack and make @​angular-devkit/build-angular optional (#​1304) (7b4a947)
• vite-plugin-angular: use JavaScript transformer from Angular Devkit for build optimizations (#​1302) (46da68a)

v1.7.2

Compare Source

Bug Fixes

• nx-plugin: add server context to Nx generator template (#​1270) (4009439)
• platform: add support for event replay with SSR (#​1277) (11631a2)
• platform: use workspace root when discovering packages for SSR transform (#​1280) (fa82328)
• router: handle cookie header internally for server data loading (#​1276) (838646c)
• update cookie interceptor in example app (#​1274) (1c209bd)
• vite-plugin-angular: use resolved config for CSS preprocessor (#​1271) (c70fdb1)
• vite-plugin-nitro: support server middleware in development (#​1269) (454889e)

v1.7.1

Compare Source

Bug Fixes

• platform: more normalization fixes (#​1259) (3c909a8)
• platform: normalize root for finding page routes on Windows (#​1255) (1e7ff22)
• router: support additional dir paths windows (#​1260) (dd0696e)
• vite-plugin-angular: include analog page files in additional compilation includes (#​1264) (bde2104)
• vitest-angular: add vitest@2 to peerDependencies (#​1252) (4964be5)

v1.7.0

Compare Source

Bug Fixes

• create-analog: add proper component naming (#​1237) (24518fc)
• platform: add workaround for redefined global in zone.js 0.14.5+ (#​1245) (9ff8a4d)
• platform: adjust transform filters for routes (#​1231) (8b488ff)
• router: correctly discover page endpoints from additional sources (#​1238) (ef2cc86)
• update peer dependencies for router and vitest-angular packages (#​1242) (5fa4205)
• vite-plugin-angular: add additionalContentDirs to analog globs (#​1246) (b0abaa2)
• vite-plugin-angular: use Vite preprocessCSS function for JIT CSS transform (#​1243) (f84bbf0)

Features

• add support for configuring additional page/content route sources (#​1228) (869cfb5)
• platform: add support for auto-discovery of SSR and optimization dependencies (#​1226) (40d03e6)
• router: provide server context awareness to routing and HttpClient requests (#​1223) (b1cdd08)

v1.6.4

Compare Source

Bug Fixes

• astro-angular: add better support for Astro environment detection (#​1229) (01d59dc)

v1.6.3

Compare Source

Bug Fixes

• astro-angular: pass Astro/Starlight defaults for esbuild (#​1219) (b29fc65)
• create-analog: typo on prism highlighter (#​1218) (eb8e753)

v1.6.2

Compare Source

Bug Fixes

• content: export prism highlighter for custom client rendering (#​1209) (768ac1a)
• create-analog: update templates to use Vite 5.x (#​1215) (5069e34)
• router: skip default export warning for redirect page routes (#​1210) (a4aa195)
• vite-plugin-angular: use Vite preprocessCSS function for component decorator styles (#​1214) (76d024b)

v1.6.1

Compare Source

Bug Fixes

• content: filter out string content when using agx files (#​1200) (c6b94ea)
• nx-plugin: add vitest types in tsconfig.spec.json (#​1197) (acaf6dc)
• router: add error message when default export is missing from component (#​1194) (4d33677)
• vite-plugin-angular: prevent context loss for "each" describe bl… (#​1195) (595a6b3)
• vite-plugin-nitro: make sitemap available for SSR build (#​1201) (90cc7bd)

v1.6.0

Compare Source

Bug Fixes

• content: import prismjs on client for prism highlighter (#​1178) (334c189)
• create-analog: add vitest-angular to package.json deps (#​1187) (65869c6)
• create-analog: correctly set package versions for yarn and pin Vite (#​1159) (847963c)
• disable esbuild if not configured to enable correct sourcemaps (#​1177) (c51e472)
• nx-plugin: set nx variable for init file template (#​1186) (e13643c)
• platform: lazy load highlighters (#​1176) (707c532)
• vite-plugin-angular: prevent context loss for "each" tests (#​1190) (13df344)
• vite-plugin-angular: prevent context loss for "each" tests (#​1190) (610f406)

Features

• content: introduce build-time rendering/highlighting for markdown (#​1174) (9ccf6b2)
• platform: add support for configuring marked, and Prism (#​1185) (79e6242)
• setup Vitest with standalone vitest-angular package (#​1184) (f6c2d00)

AssemblyScript/assemblyscript (@​assemblyscript/loader)

v0.27.29

Compare Source

Bug fixes

• std/portable included twice (#​2860) (f79391c)

Other

• chore: bump braces from 3.0.2 to 3.0.3 (#​2850) (acdb242)

v0.27.28

Compare Source

Bug fixes

• detect execution environment when loading wasm module (#​2855) (78963c5)

Other

• chore: temporary disable std/math.release.wat check in aarch64 osx (#​2856) (be49610)

evanw/esbuild (@​esbuild/linux-x64)

v0.23.1

Compare Source

• 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.

v0.23.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

• Revert the recent change to avoid bundling dependencies for node (#​3819)

  This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

  I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

  In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

• Fix preserving collapsed JSX whitespace (#​3818)

  When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

  // Original code
  <Foo>
    <Bar />
  </Foo>
  
  // Old output (with --jsx=preserve)
  <Foo><Bar /></Foo>;
  
  // New output (with --jsx=preserve)
  <Foo>
    <Bar />
  </Foo>;

v0.22.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.

• Omit packages from bundles by default when targeting node (#​1874, #​2830, #​2846, #​2915, #​3145, #​3294, #​3323, #​3582, #​3809, #​3815)

  This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

  With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

  The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

• Drop support for older platforms (#​3802)

  This release drops support for the following operating systems:

  • Windows 7
  • Windows 8
  • Windows Server 2008
  • Windows Server 2012

  This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild.exe --version
  

  In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).

• Update await using behavior to match TypeScript

  TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

• Allow es2024 as a target environment

  The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

• Publish binaries for OpenBSD on 64-bit ARM (#​3665, #​3674)

  With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

  This was contributed by @​ikmckenz.

• Publish binaries for WASI (WebAssembly System Interface) preview 1 (#​3300, #​3779)

  The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a .wasm file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).

  Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has released support for preview 1, which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.

  This release publishes esbuild precompiled for WASI preview 1 to the @esbuild/wasi-preview1 package on npm (specifically the file @esbuild/wasi-preview1/esbuild.wasm). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1.

• Warn about onResolve plugins not setting a path (#​3790)

  Plugins that return values from onResolve without resolving the path (i.e. without setting either path or external: true) will now cause a warning. This is because esbuild only uses return values from onResolve if it successfully resolves the path, and it's not good for invalid input to be silently ignored.

• Add a new Go API for running the CLI with plugins (#​3539)

  With esbuild's Go API, you can now call cli.RunWithPlugins(args, plugins) to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled.

  This was contributed by @​edewit.

ngneat/effects (@​ngneat/effects-ng)

v3.1.4

Compare Source

rollup/rollup (@​rollup/rollup-linux-x64-gnu)

v4.21.2

Compare Source

2024-08-30

Bug Fixes

• Handle IIFE/UMD namespace definitions conflicting with a builtin property (#​5605)

Pull Requests

• #​5605: fix: Wrong namespace property definition (@​thirumurugan-git, @​lukastaegert)
• #​5630: chore(deps): lock file maintenance minor/patch updates (@​renovate[bot])
• #​5631: chore(deps): lock file maintenance (@​renovate[bot])
• #​5632: chore(deps): lock file maintenance (@​renovate[bot])

v4.21.1

Compare Source

2024-08-26

Bug Fixes

• Ensure closeWatcher hook is called when watch mode is aborted via Ctrl+C (#​5618)
• Do not produce invalid code for import.meta.url in compact mode (#​5624)
• Do not throw when generating chunk names when preserving modules in Windows (#​5625)

Pull Requests

• #​5591: chore(deps): update dependency @​types/eslint to v9 (@​renovate[bot], @​lukastaegert)
• #​5618: preload the WASM file even though the version is undefined. (@​TrickyPi)
• #​5619: Call and await closeWatcher hooks on exit signals (@​lukastaegert)
• #​5622: chore(deps): lock file maintenance minor/patch updates (@​renovate[bot], @​lukastaegert)
• #​5624: fix: add space for DOCUMENT_CURRENT_SCRIPT template (@​TrickyPi)
• #​5625: fix: get the right chunk name for preserve modules in Windows (@​TrickyPi, @​lukastaegert)

v4.21.0

Compare Source

2024-08-18

Features

• Add option to configure directory for virtual modules when preserving modules (#​5602)

Pull Requests

• #​5602: feat: introduce the virtualDirname option to customize the virtual directory name (@​TrickyPi)
• #​5607: chore(deps): update typescript-eslint monorepo to v8 (major) (@​renovate[bot], @​lukastaegert)
• #​5608: chore(deps): lock file maintenance minor/patch updates (@​renovate[bot])
• #​5611: chore: fix the noConflict option in REPL. (@​7086cmd)
• #​5613: chore(deps): lock file maintenance minor/patch updates (@​renovate[bot])
• #​5614: chore(deps): lock file maintenance (@​renovate[bot])

tensorflow/tfjs (@​tensorflow/tfjs)

v4.21.0

Compare Source

ajaxorg/ace-builds (ace-builds)

v1.36.2

Compare Source

v1.36.1

[Compare Source](https://redirect.github.com/ajaxorg/a

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 84d0128. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

🟥 Failed Commands
nx affected -t=test,test-integration -c=ci

✅ Successfully ran 3 targets

• nx affected -t=e2e-ci
• nx affected -t=build,lint,component-test
• nx-cloud record -- nx format:check

---

Sent with 💌 from NxCloud.