github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-16 06:08:33 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[PR #1250] [CLOSED] Bump the dev-patch-updates group with 3 updates #7292

New Issue
Closed
opened 2026-04-25 16:10:17 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-25 16:10:17 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/fosrl/pangolin/pull/1250
Author: @dependabot[bot]
Created: 8/11/2025
Status: ❌ Closed

Base: main ← Head: dependabot/npm_and_yarn/dev-patch-updates-29f0ba4224

📝 Commits (1)

  • 94dc419 Bump the dev-patch-updates group with 3 updates

📊 Changes

2 files changed (+117 additions, -117 deletions)

View changed files

📝 package-lock.json (+115 -115)
📝 package.json (+2 -2)

📄 Description

Bumps the dev-patch-updates group with 3 updates: @types/node, @types/pg and esbuild.

Updates @types/node from 24.2.0 to 24.2.1

Commits

Updates @types/pg from 8.15.4 to 8.15.5

Commits

Updates esbuild from 0.25.6 to 0.25.8

Release notes

Sourced from esbuild's releases.

v0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

    class CachedDict {
  #has = (a: string) => dict.has(a);
  has = window
    ? (word: string): boolean => this.#has(word)
    : this.#has;
}

  • Fix a regression with the parsing of source phase imports

    The change in the previous release to parse source phase imports failed to properly handle the following cases:

    import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'

    Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

v0.25.7

  • Parse and print JavaScript imports with an explicit phase (#4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";
const bar = await import.source("<specifier>");

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

    class CachedDict {
  #has = (a: string) => dict.has(a);
  has = window
    ? (word: string): boolean => this.#has(word)
    : this.#has;
}

  • Fix a regression with the parsing of source phase imports

    The change in the previous release to parse source phase imports failed to properly handle the following cases:

    import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'

    Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

0.25.7

  • Parse and print JavaScript imports with an explicit phase (#4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";

... (truncated)

Commits
  • 8c71947 publish 0.25.8 to npm
  • 0508f24 some parsing fixes for source phase imports
  • 6e4be2f js parser: recover from bad #private identifiers
  • c9c6357 fix #4248: #private ids in arrow fn body in ?:
  • 9b42f68 publish 0.25.7 to npm
  • 9ba01d1 abs-paths: js api and tests
  • ca196c9 fix for parser backtracking crash
  • 2979b84 fix #4241: ts arrow function type backtrack (hack)
  • 1180410 fix an unused variable warning
  • fc3da57 fix #4238: add defer and source import phases
  • 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

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/fosrl/pangolin/pull/1250 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 8/11/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/dev-patch-updates-29f0ba4224` --- ### 📝 Commits (1) - [`94dc419`](https://github.com/fosrl/pangolin/commit/94dc4198554e63ef4118b10c046b5368b149ef41) Bump the dev-patch-updates group with 3 updates ### 📊 Changes **2 files changed** (+117 additions, -117 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+115 -115) 📝 `package.json` (+2 -2) </details> ### 📄 Description Bumps the dev-patch-updates group with 3 updates: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node), [@types/pg](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/pg) and [esbuild](https://github.com/evanw/esbuild). Updates `@types/node` from 24.2.0 to 24.2.1 <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare view</a></li> </ul> </details> <br /> Updates `@types/pg` from 8.15.4 to 8.15.5 <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/pg">compare view</a></li> </ul> </details> <br /> Updates `esbuild` from 0.25.6 to 0.25.8 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p> <blockquote> <h2>v0.25.8</h2> <ul> <li> <p>Fix another TypeScript parsing edge case (<a href="https://redirect.github.com/evanw/esbuild/issues/4248">#4248</a>)</p> <p>This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the <code>?:</code> operator. The regression specifically involves parsing an arrow function containing a <code>#private</code> identifier inside the middle of a <code>?:</code> ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:</p> <pre lang="ts"><code>class CachedDict { #has = (a: string) =&gt; dict.has(a); has = window ? (word: string): boolean =&gt; this.#has(word) : this.#has; } </code></pre> </li> <li> <p>Fix a regression with the parsing of source phase imports</p> <p>The change in the previous release to parse <a href="https://github.com/tc39/proposal-source-phase-imports">source phase imports</a> failed to properly handle the following cases:</p> <pre lang="ts"><code>import source from 'bar' import source from from 'bar' import source type foo from 'bar' </code></pre> <p>Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.</p> </li> </ul> <h2>v0.25.7</h2> <ul> <li> <p>Parse and print JavaScript imports with an explicit phase (<a href="https://redirect.github.com/evanw/esbuild/issues/4238">#4238</a>)</p> <p>This release adds basic syntax support for the <code>defer</code> and <code>source</code> import phases in JavaScript:</p> <ul> <li> <p><code>defer</code></p> <p>This is a <a href="https://github.com/tc39/proposal-defer-import-eval">stage 3 proposal</a> for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-9-beta/#support-for-import-defer">TypeScript 5.9</a>. The syntax looks like this:</p> <pre lang="js"><code>import defer * as foo from &quot;&lt;specifier&gt;&quot;; const bar = await import.defer(&quot;&lt;specifier&gt;&quot;); </code></pre> <p>Note that this feature deliberately cannot be used with the syntax <code>import defer foo from &quot;&lt;specifier&gt;&quot;</code> or <code>import defer { foo } from &quot;&lt;specifier&gt;&quot;</code>.</p> </li> <li> <p><code>source</code></p> <p>This is a <a href="https://github.com/tc39/proposal-source-phase-imports">stage 3 proposal</a> for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see <a href="https://redirect.github.com/microsoft/TypeScript/issues/61216">this issue</a> for details). The syntax looks like this:</p> <pre lang="js"><code>import source foo from &quot;&lt;specifier&gt;&quot;; const bar = await import.source(&quot;&lt;specifier&gt;&quot;); </code></pre> </li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's changelog</a>.</em></p> <blockquote> <h2>0.25.8</h2> <ul> <li> <p>Fix another TypeScript parsing edge case (<a href="https://redirect.github.com/evanw/esbuild/issues/4248">#4248</a>)</p> <p>This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the <code>?:</code> operator. The regression specifically involves parsing an arrow function containing a <code>#private</code> identifier inside the middle of a <code>?:</code> ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:</p> <pre lang="ts"><code>class CachedDict { #has = (a: string) =&gt; dict.has(a); has = window ? (word: string): boolean =&gt; this.#has(word) : this.#has; } </code></pre> </li> <li> <p>Fix a regression with the parsing of source phase imports</p> <p>The change in the previous release to parse <a href="https://github.com/tc39/proposal-source-phase-imports">source phase imports</a> failed to properly handle the following cases:</p> <pre lang="ts"><code>import source from 'bar' import source from from 'bar' import source type foo from 'bar' </code></pre> <p>Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.</p> </li> </ul> <h2>0.25.7</h2> <ul> <li> <p>Parse and print JavaScript imports with an explicit phase (<a href="https://redirect.github.com/evanw/esbuild/issues/4238">#4238</a>)</p> <p>This release adds basic syntax support for the <code>defer</code> and <code>source</code> import phases in JavaScript:</p> <ul> <li> <p><code>defer</code></p> <p>This is a <a href="https://github.com/tc39/proposal-defer-import-eval">stage 3 proposal</a> for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-9-beta/#support-for-import-defer">TypeScript 5.9</a>. The syntax looks like this:</p> <pre lang="js"><code>import defer * as foo from &quot;&lt;specifier&gt;&quot;; const bar = await import.defer(&quot;&lt;specifier&gt;&quot;); </code></pre> <p>Note that this feature deliberately cannot be used with the syntax <code>import defer foo from &quot;&lt;specifier&gt;&quot;</code> or <code>import defer { foo } from &quot;&lt;specifier&gt;&quot;</code>.</p> </li> <li> <p><code>source</code></p> <p>This is a <a href="https://github.com/tc39/proposal-source-phase-imports">stage 3 proposal</a> for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see <a href="https://redirect.github.com/microsoft/TypeScript/issues/61216">this issue</a> for details). The syntax looks like this:</p> <pre lang="js"><code>import source foo from &quot;&lt;specifier&gt;&quot;; </code></pre> </li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/8c71947edbe5a158fec3a6d1cbfea1e8d5cdee70"><code>8c71947</code></a> publish 0.25.8 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/0508f2444569ba105fa38e6e9fa9e1f2ed6d95b2"><code>0508f24</code></a> some parsing fixes for source phase imports</li> <li><a href="https://github.com/evanw/esbuild/commit/6e4be2fad3c898ea2f4d9c2fd0be7bbcd79f5206"><code>6e4be2f</code></a> js parser: recover from bad <code>#private</code> identifiers</li> <li><a href="https://github.com/evanw/esbuild/commit/c9c6357a8dbf43b9ec2896bd92e25df2f0677b45"><code>c9c6357</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4248">#4248</a>: <code>#private</code> ids in arrow fn body in <code>?:</code></li> <li><a href="https://github.com/evanw/esbuild/commit/9b42f68f9b1fecf16e72dbcfc5c46504239d6fe6"><code>9b42f68</code></a> publish 0.25.7 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/9ba01d1c1faf6f157d614c64144193dbfe88db97"><code>9ba01d1</code></a> abs-paths: js api and tests</li> <li><a href="https://github.com/evanw/esbuild/commit/ca196c9c4a270ff61181bc8d61886b947bbc2612"><code>ca196c9</code></a> fix for parser backtracking crash</li> <li><a href="https://github.com/evanw/esbuild/commit/2979b846fd7e5899a57f412bb3ce8ee0c8c150f3"><code>2979b84</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4241">#4241</a>: ts arrow function type backtrack (hack)</li> <li><a href="https://github.com/evanw/esbuild/commit/1180410e335f49eb8a4b33be4357bf15b185475e"><code>1180410</code></a> fix an unused variable warning</li> <li><a href="https://github.com/evanw/esbuild/commit/fc3da579557d775c022dbfc4e68843d34cab9fb5"><code>fc3da57</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4238">#4238</a>: add <code>defer</code> and <code>source</code> import phases</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.25.6...v0.25.8">compare view</a></li> </ul> </details> <br /> 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-25 16:10:17 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#7292
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?