Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump github.com/evanw/esbuild from 0.13.7 to 0.13.9 #52

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 25, 2021

Bumps github.com/evanw/esbuild from 0.13.7 to 0.13.9.

Release notes

Sourced from github.com/evanw/esbuild's releases.

v0.13.9

  • Add support for imports in package.json (#1691)

    This release adds basic support for the imports field in package.json. It behaves similarly to the exports field but only applies to import paths that start with #. The imports field provides a way for a package to remap its own internal imports for itself, while the exports field provides a way for a package to remap its external exports for other packages. This is useful because the imports field respects the currently-configured conditions which means that the import mapping can change at run-time. For example:

    $ cat entry.mjs
    import '#example'
    

    $ cat package.json { "imports": { "#example": { "foo": "./example.foo.mjs", "default": "./example.mjs" } } }

    $ cat example.foo.mjs console.log('foo is enabled')

    $ cat example.mjs console.log('foo is disabled')

    $ node entry.mjs foo is disabled

    $ node --conditions=foo entry.mjs foo is enabled

    Now that esbuild supports this feature too, import paths starting with # and any provided conditions will be respected when bundling:

    $ esbuild --bundle entry.mjs | node
    foo is disabled
    

    $ esbuild --conditions=foo --bundle entry.mjs | node foo is enabled

  • Fix using npm rebuild with the esbuild package (#1703)

    Version 0.13.4 accidentally introduced a regression in the install script where running npm rebuild multiple times could fail after the second time. The install script creates a copy of the binary executable using link followed by rename. Using link creates a hard link which saves space on the file system, and rename is used for safety since it atomically replaces the destination.

    However, the rename syscall has an edge case where it silently fails if the source and destination are both the same link. This meant that the install script would fail after being run twice in a row. With this release, the install script now deletes the source after calling rename in case it has silently failed, so this issue should now be fixed. It should now be safe to use npm rebuild with the esbuild package.

  • Fix invalid CSS minification of border-radius (#1702)

... (truncated)

Changelog

Sourced from github.com/evanw/esbuild's changelog.

0.13.9

  • Add support for imports in package.json (#1691)

    This release adds basic support for the imports field in package.json. It behaves similarly to the exports field but only applies to import paths that start with #. The imports field provides a way for a package to remap its own internal imports for itself, while the exports field provides a way for a package to remap its external exports for other packages. This is useful because the imports field respects the currently-configured conditions which means that the import mapping can change at run-time. For example:

    $ cat entry.mjs
    import '#example'
    

    $ cat package.json { "imports": { "#example": { "foo": "./example.foo.mjs", "default": "./example.mjs" } } }

    $ cat example.foo.mjs console.log('foo is enabled')

    $ cat example.mjs console.log('foo is disabled')

    $ node entry.mjs foo is disabled

    $ node --conditions=foo entry.mjs foo is enabled

    Now that esbuild supports this feature too, import paths starting with # and any provided conditions will be respected when bundling:

    $ esbuild --bundle entry.mjs | node
    foo is disabled
    

    $ esbuild --conditions=foo --bundle entry.mjs | node foo is enabled

  • Fix using npm rebuild with the esbuild package (#1703)

    Version 0.13.4 accidentally introduced a regression in the install script where running npm rebuild multiple times could fail after the second time. The install script creates a copy of the binary executable using link followed by rename. Using link creates a hard link which saves space on the file system, and rename is used for safety since it atomically replaces the destination.

    However, the rename syscall has an edge case where it silently fails if the source and destination are both the same link. This meant that the install script would fail after being run twice in a row. With this release, the install script now deletes the source after calling rename in case it has silently failed, so this issue should now be fixed. It should now be safe to use npm rebuild with the esbuild package.

  • Fix invalid CSS minification of border-radius (#1702)

... (truncated)

Commits

Dependabot compatibility score

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)

Bumps [github.com/evanw/esbuild](https://github.com/evanw/esbuild) from 0.13.7 to 0.13.9.
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/master/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.13.7...v0.13.9)

---
updated-dependencies:
- dependency-name: github.com/evanw/esbuild
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 25, 2021
@codecov-commenter
Copy link

codecov-commenter commented Oct 25, 2021

Codecov Report

Merging #52 (5ae4142) into main (4055ee5) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main      #52   +/-   ##
=======================================
  Coverage   50.02%   50.02%           
=======================================
  Files          14       14           
  Lines        1693     1693           
=======================================
  Hits          847      847           
  Misses        801      801           
  Partials       45       45           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4055ee5...5ae4142. Read the comment docs.

@rodrigo-brito rodrigo-brito merged commit a3790f0 into main Oct 25, 2021
@rodrigo-brito rodrigo-brito deleted the dependabot/go_modules/github.com/evanw/esbuild-0.13.9 branch October 25, 2021 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants