build(deps-dev): bump esbuild from 0.14.54 to 0.15.5 in /packages/xicons-site

[dependabot[bot]]

Bumps esbuild from 0.14.54 to 0.15.5.

Release notes

Sourced from esbuild's releases.

v0.15.5

• Fix issues with Yarn PnP and Yarn's workspaces feature (#2476)

  This release makes sure esbuild works with a Yarn feature called workspaces. Previously esbuild wasn't tested in this scenario, but this scenario now has test coverage. Getting this to work involved further tweaks to esbuild's custom code for what happens after Yarn PnP's path resolution algorithm runs, which is not currently covered by Yarn's PnP specification. These tweaks also fix exports map resolution with Yarn PnP for non-empty subpaths, which wasn't previously working.

v0.15.4

• Consider TypeScript import assignments to be side-effect free (#2468)

  TypeScript has a legacy import syntax for working with TypeScript namespaces that looks like this:

  import { someNamespace } from './some-file'
  import bar = someNamespace.foo;
  // some-file.ts
  export namespace someNamespace {
  export let foo = 123
  }
  

  Since esbuild converts TypeScript into JavaScript one file at a time, it doesn't know if bar is supposed to be a value or a type (or both, which TypeScript actually allows in this case). This is problematic because values are supposed to be kept during the conversion but types are supposed to be removed during the conversion. Currently esbuild keeps bar in the output, which is done because someNamespace.foo is a property access and property accesses run code that could potentially have a side effect (although there is no side effect in this case).

  With this release, esbuild will now consider someNamespace.foo to have no side effects. This means bar will now be removed when bundling and when tree shaking is enabled. Note that it will still not be removed when tree shaking is disabled. This is because in this mode, esbuild supports adding additional code to the end of the generated output that's in the same scope as the module. That code could potentially make use of bar, so it would be incorrect to remove it. If you want bar to be removed, you'll have to enable tree shaking (which tells esbuild that nothing else depends on the unexported top-level symbols in the generated output).

• Change the order of the banner and the "use strict" directive (#2467)

  Previously the top of the file contained the following things in order:

  1. The hashbang comment (see below) from the source code, if present
  2. The "use strict" directive from the source code, if present
  3. The content of esbuild's banner API option, if specified

  This was problematic for people that used the banner API option to insert the hashbang comment instead of using esbuild's hashbang comment preservation feature. So with this release, the order has now been changed to:

  1. The hashbang comment (see below) from the source code, if present
  2. The content of esbuild's banner API option, if specified
  3. The "use strict" directive from the source code, if present

  I'm considering this change to be a bug fix instead of a breaking change because esbuild's documentation states that the banner API option can be used to "insert an arbitrary string at the beginning of generated JavaScript files". While this isn't technically true because esbuild may still insert the original hashbang comment before the banner, it's at least more correct now because the banner will now come before the "use strict" directive.

  For context: JavaScript files recently allowed using a hashbang comment, which starts with #! and which must start at the very first character of the file. It allows Unix systems to execute the file directly as a script without needing to prefix it by the node command. This comment typically has the value #!/usr/bin/env node. Hashbang comments will be a part of ES2023 when it's released next year.

• Fix exports maps with Yarn PnP path resolution (#2473)

  The Yarn PnP specification says that to resolve a package path, you first resolve it to the absolute path of a directory, and then you run node's module resolution algorithm on it. Previously esbuild followed this part of the specification. However, doing this means that exports in package.json is not respected because node's module resolution algorithm doesn't interpret exports for absolute paths. So with this release, esbuild will now use a modified algorithm that deviates from both specifications but that should hopefully behave more similar to what Yarn actually does: node's module resolution algorithm is run with the original import path but starting from the directory returned by Yarn PnP.

v0.15.3

• Change the Yarn PnP manifest to a singleton (#2463)

  Previously esbuild searched for the Yarn PnP manifest in the parent directories of each file. But with Yarn's enableGlobalCache setting it's possible to configure Yarn PnP's implementation to reach outside of the directory subtree containing the Yarn PnP manifest. This was causing esbuild to fail to bundle projects with the enableGlobalCache setting enabled.

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.15.5

• Fix issues with Yarn PnP and Yarn's workspaces feature (#2476)

  This release makes sure esbuild works with a Yarn feature called workspaces. Previously esbuild wasn't tested in this scenario, but this scenario now has test coverage. Getting this to work involved further tweaks to esbuild's custom code for what happens after Yarn PnP's path resolution algorithm runs, which is not currently covered by Yarn's PnP specification. These tweaks also fix exports map resolution with Yarn PnP for non-empty subpaths, which wasn't previously working.

0.15.4

• Consider TypeScript import assignments to be side-effect free (#2468)

  TypeScript has a legacy import syntax for working with TypeScript namespaces that looks like this:

  import { someNamespace } from './some-file'
  import bar = someNamespace.foo;
  // some-file.ts
  export namespace someNamespace {
  export let foo = 123
  }
  

  Since esbuild converts TypeScript into JavaScript one file at a time, it doesn't know if bar is supposed to be a value or a type (or both, which TypeScript actually allows in this case). This is problematic because values are supposed to be kept during the conversion but types are supposed to be removed during the conversion. Currently esbuild keeps bar in the output, which is done because someNamespace.foo is a property access and property accesses run code that could potentially have a side effect (although there is no side effect in this case).

  With this release, esbuild will now consider someNamespace.foo to have no side effects. This means bar will now be removed when bundling and when tree shaking is enabled. Note that it will still not be removed when tree shaking is disabled. This is because in this mode, esbuild supports adding additional code to the end of the generated output that's in the same scope as the module. That code could potentially make use of bar, so it would be incorrect to remove it. If you want bar to be removed, you'll have to enable tree shaking (which tells esbuild that nothing else depends on the unexported top-level symbols in the generated output).

• Change the order of the banner and the "use strict" directive (#2467)

  Previously the top of the file contained the following things in order:

  1. The hashbang comment (see below) from the source code, if present
  2. The "use strict" directive from the source code, if present
  3. The content of esbuild's banner API option, if specified

  This was problematic for people that used the banner API option to insert the hashbang comment instead of using esbuild's hashbang comment preservation feature. So with this release, the order has now been changed to:

  1. The hashbang comment (see below) from the source code, if present
  2. The content of esbuild's banner API option, if specified
  3. The "use strict" directive from the source code, if present

  I'm considering this change to be a bug fix instead of a breaking change because esbuild's documentation states that the banner API option can be used to "insert an arbitrary string at the beginning of generated JavaScript files". While this isn't technically true because esbuild may still insert the original hashbang comment before the banner, it's at least more correct now because the banner will now come before the "use strict" directive.

  For context: JavaScript files recently allowed using a hashbang comment, which starts with #! and which must start at the very first character of the file. It allows Unix systems to execute the file directly as a script without needing to prefix it by the node command. This comment typically has the value #!/usr/bin/env node. Hashbang comments will be a part of ES2023 when it's released next year.

• Fix exports maps with Yarn PnP path resolution (#2473)

  The Yarn PnP specification says that to resolve a package path, you first resolve it to the absolute path of a directory, and then you run node's module resolution algorithm on it. Previously esbuild followed this part of the specification. However, doing this means that exports in package.json is not respected because node's module resolution algorithm doesn't interpret exports for absolute paths. So with this release, esbuild will now use a modified algorithm that deviates from both specifications but that should hopefully behave more similar to what Yarn actually does: node's module resolution algorithm is run with the original import path but starting from the directory returned by Yarn PnP.

0.15.3

... (truncated)

Commits

• a6c42a1 publish 0.15.5 to npm
• 9eb3302 fix #2476: issues with yarn's "workspaces" feature
• f4da27c publish 0.15.4 to npm
• 6a69a18 fix #2473: yarn pnp exports in package.json
• 5e085f5 Suggest using Number.isNaN instead of isNaN (#2471)
• 13587ce fix #2468: allow ts import x = to be tree shaken
• 6d4f902 fix #2467: move banner before "use strict"
• eeb2509 publish 0.15.3 to npm
• 8a71011 pnp: remove unused dependencyTreeRoots data
• 44a7a61 fix #2463: change yarn pnp manifest to a singleton
• 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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
xicons	❌ Failed (Inspect)		Aug 17, 2022 at 5:08AM (UTC)

[dependabot[bot]]

Superseded by #535.