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: update all non-major dependencies #22538

Merged
merged 1 commit into from
Jan 21, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 21, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/preset-env (source) 7.16.10 -> 7.16.11 age adoption passing confidence
copy-webpack-plugin 10.2.0 -> 10.2.1 age adoption passing confidence
esbuild 0.14.11 -> 0.14.12 age adoption passing confidence
esbuild-wasm 0.14.11 -> 0.14.12 age adoption passing confidence
resolve 1.21.0 -> 1.21.1 age adoption passing confidence

Release Notes

babel/babel

v7.16.11

Compare Source

v7.16.11 (2022-01-20)

This empty releases force-publishes a new version of @babel/plugin-proposal-private-methods (which was not published in v7.16.10 because it didn't have any actual change) and of @babel/preset-env.

This solves an incompatibility between @babel/preset-env@7.16.10 and @babel/helper-create-class-features-plugin@7.16.7, by making sure that @babel/preset-env transitively depends on @babel/helper-create-class-features-plugin@^7.16.10.

webpack-contrib/copy-webpack-plugin

v10.2.1

Compare Source

evanw/esbuild

v0.14.12

Compare Source

  • 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 <div>></div>;
            │               ^
            ╵               {'>'}
    
      Did you mean to escape it as "{'>'}" instead?
    
    ✘ [ERROR] The character "}" is not valid inside a JSX element
    
        example.tsx:5:17:
          5 │   return <div>{1}}</div>;
            │                  ^
            ╵                  {'}'}
    
      Did you mean to escape it as "{'}'}" instead?
    

    Babel doesn't yet treat this as an error, so esbuild only warns about these characters in JavaScript files for now. Babel 8 treats this as an error but Babel 8 hasn't been released yet. If you see this warning, I recommend fixing the invalid JSX syntax because it will become an error in the future.

  • Warn about basic CSS property typos

    This release now generates a warning if you use a CSS property that is one character off from a known CSS property:

    ▲ [WARNING] "marign-left" is not a known CSS property
    
        example.css:2:2:
          2 │   marign-left: 12px;
            │   ~~~~~~~~~~~
            ╵   margin-left
    
      Did you mean "margin-left" instead?
    
browserify/resolve

v1.21.1

Compare Source


Configuration

📅 Schedule: "after 10pm every weekday,before 4am every weekday,every weekend" in timezone America/Tijuana.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release labels Jan 21, 2022
@alan-agius4 alan-agius4 added target: rc This PR is targeted for the next release-candidate and removed target: minor This PR is targeted for the next minor release labels Jan 21, 2022
@alan-agius4 alan-agius4 merged commit f8eb40e into master Jan 21, 2022
@renovate renovate bot deleted the renovate/all-minor-patch branch January 21, 2022 11:53
@renovate renovate bot restored the renovate/all-minor-patch branch January 21, 2022 19:59
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants