build: update all non-major dependencies

[angular-robot]

This PR contains the following updates:

Package	Type	Update	Change
esbuild	optionalDependencies	patch	0.18.11 -> 0.18.12
esbuild	devDependencies	patch	0.18.11 -> 0.18.12
esbuild-wasm	dependencies	patch	0.18.11 -> 0.18.12
esbuild-wasm	devDependencies	patch	0.18.11 -> 0.18.12
postcss (source)	dependencies	patch	8.4.25 -> 8.4.26
postcss (source)	devDependencies	patch	8.4.25 -> 8.4.26

---

Release Notes

evanw/esbuild (esbuild)

v0.18.12

Compare Source

• Fix a panic with const enum inside parentheses (#​3205)

  This release fixes an edge case where esbuild could potentially panic if a TypeScript const enum statement was used inside of a parenthesized expression and was followed by certain other scope-related statements. Here's a minimal example that triggers this edge case:

  (() => {
    const enum E { a };
    () => E.a
  })

• Allow a newline in the middle of TypeScript export type statement (#​3225)

  Previously esbuild incorrectly rejected the following valid TypeScript code:

  export type
  { T };
  
  export type
  * as foo from 'bar';

  Code that uses a newline after export type is now allowed starting with this release.

• Fix cross-module inlining of string enums (#​3210)

  A refactoring typo in version 0.18.9 accidentally introduced a regression with cross-module inlining of string enums when combined with computed property accesses. This regression has been fixed.

• Rewrite .js to .ts inside packages with exports (#​3201)

  Packages with the exports field are supposed to disable node's path resolution behavior that allows you to import a file with a different extension than the one in the source code (for example, importing foo/bar to get foo/bar.js). And TypeScript has behavior where you can import a non-existent .js file and you will get the .ts file instead. Previously the presence of the exports field caused esbuild to disable all extension manipulation stuff which included both node's implicit file extension searching and TypeScript's file extension swapping. However, TypeScript appears to always apply file extension swapping even in this case. So with this release, esbuild will now rewrite .js to .ts even inside packages with exports.

• Fix a redirect edge case in esbuild's development server (#​3208)

  The development server canonicalizes directory URLs by adding a trailing slash. For example, visiting /about redirects to /about/ if /about/index.html would be served. However, if the requested path begins with two slashes, then the redirect incorrectly turned into a protocol-relative URL. For example, visiting //about redirected to //about/ which the browser turns into http://about/. This release fixes the bug by canonicalizing the URL path when doing this redirect.

postcss/postcss (postcss)

v8.4.26

Compare Source

• Fixed clone methods types.

---

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 4:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 Renovate Bot.

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     conflicts with base branch "main"
     status "ci/circleci: build" is failing
     status "ci/circleci: setup" is failing
     status "mergeability" is failing
If you want your PR to be merged, it has to pass all the CI checks.
If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}