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

chore(deps): update all non-major dependencies #56

Merged
merged 1 commit into from
Aug 14, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 14, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ^18.17.4 -> ^18.17.5 age adoption passing confidence
esbuild ^0.19.0 -> ^0.19.1 age adoption passing confidence
eslint (source) ^8.46.0 -> ^8.47.0 age adoption passing confidence

Release Notes

evanw/esbuild (esbuild)

v0.19.1

Compare Source

  • Fix a regression with baseURL in tsconfig.json (#​3307)

    The previous release moved tsconfig.json path resolution before --packages=external checks to allow the paths field in tsconfig.json to avoid a package being marked as external. However, that reordering accidentally broke the behavior of the baseURL field from tsconfig.json. This release moves these path resolution rules around again in an attempt to allow both of these cases to work.

  • Parse TypeScript type arguments for JavaScript decorators (#​3308)

    When parsing JavaScript decorators in TypeScript (i.e. with experimentalDecorators disabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example:

    @&#8203;foo<number>
    @&#8203;bar<number, string>()
    class Foo {}
  • Fix glob patterns matching extra stuff at the end (#​3306)

    Previously glob patterns such as ./*.js would incorrectly behave like ./*.js* during path matching (also matching .js.map files, for example). This was never intentional behavior, and has now been fixed.

  • Change the permissions of esbuild's generated output files (#​3285)

    This release changes the permissions of the output files that esbuild generates to align with the default behavior of node's fs.writeFileSync function. Since most tools written in JavaScript use fs.writeFileSync, this should make esbuild more consistent with how other JavaScript build tools behave.

    The full Unix-y details: Unix permissions use three-digit octal notation where the three digits mean "user, group, other" in that order. Within a digit, 4 means "read" and 2 means "write" and 1 means "execute". So 6 == 4 + 2 == read + write. Previously esbuild uses 0644 permissions (the leading 0 means octal notation) but the permissions for fs.writeFileSync defaults to 0666, so esbuild will now use 0666 permissions. This does not necessarily mean that the files esbuild generates will end up having 0666 permissions, however, as there is another Unix feature called "umask" where the operating system masks out some of these bits. If your umask is set to 0022 then the generated files will have 0644 permissions, and if your umask is set to 0002 then the generated files will have 0664 permissions.

  • Fix a subtle CSS ordering issue with @import and @layer

    With this release, esbuild may now introduce additional @layer rules when bundling CSS to better preserve the layer ordering of the input code. Here's an example of an edge case where this matters:

    /* entry.css */
    @&#8203;import "a.css";
    @&#8203;import "b.css";
    @&#8203;import "a.css";
    /* a.css */
    @&#8203;layer a {
      body {
        background: red;
      }
    }
    /* b.css */
    @&#8203;layer b {
      body {
        background: green;
      }
    }

    This CSS should set the body background to green, which is what happens in the browser. Previously esbuild generated the following output which incorrectly sets the body background to red:

    /* b.css */
    @&#8203;layer b {
      body {
        background: green;
      }
    }
    
    /* a.css */
    @&#8203;layer a {
      body {
        background: red;
      }
    }

    This difference in behavior is because the browser evaluates a.css + b.css + a.css (in CSS, each @import is replaced with a copy of the imported file) while esbuild was only writing out b.css + a.css. The first copy of a.css wasn't being written out by esbuild for two reasons: 1) bundlers care about code size and try to avoid emitting duplicate CSS and 2) when there are multiple copies of a CSS file, normally only the last copy matters since the last declaration with equal specificity wins in CSS.

    However, @layer was recently added to CSS and for @layer the first copy matters because layers are ordered using their first location in source code order. This introduction of @layer means esbuild needs to change its bundling algorithm. An easy solution would be for esbuild to write out a.css twice, but that would be inefficient. So what I'm going to try to have esbuild do with this release is to write out an abbreviated form of the first copy of a CSS file that only includes the @layer information, and then still only write out the full CSS file once for the last copy. So esbuild's output for this edge case now looks like this:

    /* a.css */
    @&#8203;layer a;
    
    /* b.css */
    @&#8203;layer b {
      body {
        background: green;
      }
    }
    
    /* a.css */
    @&#8203;layer a {
      body {
        background: red;
      }
    }

    The behavior of the bundled CSS now matches the behavior of the unbundled CSS. You may be wondering why esbuild doesn't just write out a.css first followed by b.css. That would work in this case but it doesn't work in general because for any rules outside of a @layer rule, the last copy should still win instead of the first copy.

  • Fix a bug with esbuild's TypeScript type definitions (#​3299)

    This release fixes a copy/paste error with the TypeScript type definitions for esbuild's JS API:

     export interface TsconfigRaw {
       compilerOptions?: {
    -    baseUrl?: boolean
    +    baseUrl?: string
         ...
       }
     }

    This fix was contributed by @​privatenumber.

eslint/eslint (eslint)

v8.47.0

Compare Source

Features

  • 53d7508 feat: update regex for methods with thisArg (#​17439) (Francesco Trotta)

Bug Fixes

  • 631648e fix: do not report on shadowed constructors in no-new-wrappers (#​17447) (Francesco Trotta)

Documentation

Chores


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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, check this box

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

@codecov
Copy link

codecov bot commented Aug 14, 2023

Codecov Report

Merging #56 (75b1e9c) into main (a4e7c36) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   87.50%   87.50%           
=======================================
  Files           1        1           
  Lines          24       24           
  Branches        3        3           
=======================================
  Hits           21       21           
  Partials        3        3           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@renovate renovate bot changed the title chore(deps): update dependency eslint to ^8.47.0 chore(deps): update all non-major dependencies Aug 14, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ca9ebd9 to 75b1e9c Compare August 14, 2023 19:44
@renovate renovate bot merged commit f631caf into main Aug 14, 2023
@renovate renovate bot deleted the renovate/all-minor-patch branch August 14, 2023 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants