Skip to content

chore: bump esbuild from 0.14.10 to 0.14.12#90

Closed
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/esbuild-0.14.12
Closed

chore: bump esbuild from 0.14.10 to 0.14.12#90
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/esbuild-0.14.12

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 21, 2022

Bumps esbuild from 0.14.10 to 0.14.12.

Release notes

Sourced from esbuild's releases.

v0.14.12

  • Ignore invalid @import rules in CSS (#1946)

    In CSS, @import rules must come first before any other kind of rule (except for @charset rules). Previously esbuild would warn about incorrectly ordered @import rules and then hoist them to the top of the file. This broke people who wrote invalid @import rules in the middle of their files and then relied on them being ignored. With this release, esbuild will now ignore invalid @import rules and pass them through unmodified. This more accurately follows the CSS specification. Note that this behavior differs from other tools like Parcel, which does hoist CSS @import rules.

  • Print invalid CSS differently (#1947)

    This changes how esbuild prints nested @import statements that are missing a trailing ;, which is invalid CSS. The result is still partially invalid CSS, but now printed in a better-looking way:

    /* Original code */
    .bad { @import url("other") }
    .red { background: red; }
    /* Old output (with --minify) */
    .bad{@​import url(other) } .red{background: red;}}
    /* New output (with --minify) */
    .bad{@​import url(other);}.red{background:red}

  • Warn about CSS nesting syntax (#1945)

    There's a proposed CSS syntax for nesting rules using the & selector, but it's not currently implemented in any browser. Previously esbuild silently passed the syntax through untransformed. With this release, esbuild will now warn when you use nesting syntax with a --target= setting that includes a browser.

  • Warn about } and > inside JSX elements

    The } and > characters are invalid inside JSX elements according to the JSX specification because they commonly result from typos like these that are hard to catch in code reviews:

    function F() {
      return <div>></div>;
    }
    function G() {
      return <div>{1}}</div>;
    }

    The TypeScript compiler already treats this as an error, so esbuild now treats this as an error in TypeScript files too. That looks like this:

    ✘ [ERROR] The character ">" is not valid inside a JSX element
    
    example.tsx:2:14:
      2 │   return &lt;div&gt;&gt;&lt;/div&gt;;
        │               ^
        ╵               {'&gt;'}
    

    Did you mean to escape it as "{'>'}" instead?

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.14.12

  • Ignore invalid @import rules in CSS (#1946)

    In CSS, @import rules must come first before any other kind of rule (except for @charset rules). Previously esbuild would warn about incorrectly ordered @import rules and then hoist them to the top of the file. This broke people who wrote invalid @import rules in the middle of their files and then relied on them being ignored. With this release, esbuild will now ignore invalid @import rules and pass them through unmodified. This more accurately follows the CSS specification. Note that this behavior differs from other tools like Parcel, which does hoist CSS @import rules.

  • Print invalid CSS differently (#1947)

    This changes how esbuild prints nested @import statements that are missing a trailing ;, which is invalid CSS. The result is still partially invalid CSS, but now printed in a better-looking way:

    /* Original code */
    .bad { @import url("other") }
    .red { background: red; }
    /* Old output (with --minify) */
    .bad{@​import url(other) } .red{background: red;}}
    /* New output (with --minify) */
    .bad{@​import url(other);}.red{background:red}

  • Warn about CSS nesting syntax (#1945)

    There's a proposed CSS syntax for nesting rules using the & selector, but it's not currently implemented in any browser. Previously esbuild silently passed the syntax through untransformed. With this release, esbuild will now warn when you use nesting syntax with a --target= setting that includes a browser.

  • Warn about } and > inside JSX elements

    The } and > characters are invalid inside JSX elements according to the JSX specification because they commonly result from typos like these that are hard to catch in code reviews:

    function F() {
      return <div>></div>;
    }
    function G() {
      return <div>{1}}</div>;
    }

    The TypeScript compiler already treats this as an error, so esbuild now treats this as an error in TypeScript files too. That looks like this:

    ✘ [ERROR] The character ">" is not valid inside a JSX element
    
    example.tsx:2:14:
      2 │   return &lt;div&gt;&gt;&lt;/div&gt;;
        │               ^
        ╵               {'&gt;'}
    

    Did you mean to escape it as "{'>'}" instead?

... (truncated)

Commits
  • 4276739 publish 0.14.12 to npm
  • eaa3ba8 guard typo detector access behind a mutex
  • 2f6d5fa don't try to correct CSS variables to properties
  • 5859f8c only allow CSS nesting syntax inside a style rule
  • 89fa021 warn about basic CSS property typos
  • 41dea66 small adjustment to try.html
  • 78e0808 warn about } and > inside JSX elements
  • 11ed34e allow trailing "&" nesting selectors without space
  • 69996b4 add initial support for "@​nest" rules (#1945)
  • 9851b5a warn when CSS nesting syntax is used (#1945)
  • Additional commits viewable in compare view

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 [esbuild](https://github.com/evanw/esbuild) from 0.14.10 to 0.14.12.
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/master/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.14.10...v0.14.12)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-type: direct:development
  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 Jan 21, 2022
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 24, 2022

Superseded by #91.

@dependabot dependabot bot closed this Jan 24, 2022
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/esbuild-0.14.12 branch January 24, 2022 09:01
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.

0 participants