chore(deps-dev): bump esbuild from 0.12.11 to 0.12.14

[dependabot-preview[bot]]

Bumps esbuild from 0.12.11 to 0.12.14.

Release notes

Sourced from esbuild's releases.

v0.12.14

• Fix the file loader with custom namespaces (#1404)

  This fixes a regression from version 0.12.12 where using a plugin to load an input file with the file loader in a custom namespace caused esbuild to write the contents of that input file to the path associated with that namespace instead of to a path inside of the output directory. With this release, the file loader should now always copy the file somewhere inside of the output directory.

v0.12.13

• Fix using JS synchronous API from from non-main threads (#1406)

  This release fixes an issue with the new implementation of the synchronous JS API calls (transformSync and buildSync) when they are used from a thread other than the main thread. The problem happened because esbuild's new implementation uses node's worker_threads library internally and non-main threads were incorrectly assumed to be esbuild's internal thread instead of potentially another unrelated thread. Now esbuild's synchronous JS APIs should work correctly when called from non-main threads.

v0.12.12

• Fix file loader import paths when subdirectories are present (#1044)

  Using the file loader for a file type causes importing affected files to copy the file into the output directory and to embed the path to the copied file into the code that imported it. However, esbuild previously always embedded the path relative to the output directory itself. This is problematic when the importing code is generated within a subdirectory inside the output directory, since then the relative path is wrong. For example:

  $ cat src/example/entry.css
  div {
    background: url(../images/image.png);
  }
  $ esbuild --bundle src/example/entry.css --outdir=out --outbase=src --loader:.png=file
  $ find out -type f
  out/example/entry.css
  out/image-55DNWN2R.png
  $ cat out/example/entry.css
  /* src/example/entry.css */
  div {
  background: url(./image-55DNWN2R.png);
  }
  

  This is output from the previous version of esbuild. The above asset reference in out/example/entry.css is wrong. The path should start with ../ because the two files are in different directories.

  With this release, the asset references present in output files will now be the full relative path from the output file to the asset, so imports should now work correctly when the entry point is in a subdirectory within the output directory. This change affects asset reference paths in both CSS and JS output files.

  Note that if you want asset reference paths to be independent of the subdirectory in which they reside, you can use the --public-path setting to provide the common path that all asset reference paths should be constructed relative to. Specifically --public-path=. should bring back the old problematic behavior in case you need it.

• Add support for [dir] in --asset-names (#1196)

  You can now use path templates such as --asset-names=[dir]/[name]-[hash] to copy the input directory structure of your asset files (i.e. input files loaded with the file loader) to the output directory. Here's an example:

  $ cat entry.css
  header {
    background: url(images/common/header.png);
  }
  main {
  

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.12.14

• Fix the file loader with custom namespaces (#1404)

  This fixes a regression from version 0.12.12 where using a plugin to load an input file with the file loader in a custom namespace caused esbuild to write the contents of that input file to the path associated with that namespace instead of to a path inside of the output directory. With this release, the file loader should now always copy the file somewhere inside of the output directory.

0.12.13

• Fix using JS synchronous API from from non-main threads (#1406)

  This release fixes an issue with the new implementation of the synchronous JS API calls (transformSync and buildSync) when they are used from a thread other than the main thread. The problem happened because esbuild's new implementation uses node's worker_threads library internally and non-main threads were incorrectly assumed to be esbuild's internal thread instead of potentially another unrelated thread. Now esbuild's synchronous JS APIs should work correctly when called from non-main threads.

0.12.12

• Fix file loader import paths when subdirectories are present (#1044)

  Using the file loader for a file type causes importing affected files to copy the file into the output directory and to embed the path to the copied file into the code that imported it. However, esbuild previously always embedded the path relative to the output directory itself. This is problematic when the importing code is generated within a subdirectory inside the output directory, since then the relative path is wrong. For example:

  $ cat src/example/entry.css
  div {
    background: url(../images/image.png);
  }
  $ esbuild --bundle src/example/entry.css --outdir=out --outbase=src --loader:.png=file
  $ find out -type f
  out/example/entry.css
  out/image-55DNWN2R.png
  $ cat out/example/entry.css
  /* src/example/entry.css */
  div {
  background: url(./image-55DNWN2R.png);
  }
  

  This is output from the previous version of esbuild. The above asset reference in out/example/entry.css is wrong. The path should start with ../ because the two files are in different directories.

  With this release, the asset references present in output files will now be the full relative path from the output file to the asset, so imports should now work correctly when the entry point is in a subdirectory within the output directory. This change affects asset reference paths in both CSS and JS output files.

  Note that if you want asset reference paths to be independent of the subdirectory in which they reside, you can use the --public-path setting to provide the common path that all asset reference paths should be constructed relative to. Specifically --public-path=. should bring back the old problematic behavior in case you need it.

• Add support for [dir] in --asset-names (#1196)

  You can now use path templates such as --asset-names=[dir]/[name]-[hash] to copy the input directory structure of your asset files (i.e. input files loaded with the file loader) to the output directory. Here's an example:

  $ cat entry.css
  header {
  

... (truncated)

Commits

• bf72f26 publish 0.12.14 to npm
• 963ce60 fix #1404: "file" loader always copies to "outdir"
• 67f61ba pull out relative-to-outbase code
• aa4646f factor out some code related to "outfile"
• 4a6e106 keep wasm tests self-contained
• 1311305 publish 0.12.13 to npm
• d12fade Fix using JS synchronous API from from non-main threads (#1411)
• b63ebbf publish 0.12.12 to npm
• d4ce259 fix a windows path issue
• c7be8d8 fix #1044: correct relative paths for file loader
• 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.

If all status checks pass Dependabot will automatically merge this pull request.

---

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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

• LGTM analysis: JavaScript

Dependabot will still automatically merge this pull request if you amend it and your tests pass.