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

Update all dependencies #510

Merged
merged 1 commit into from
Apr 1, 2023
Merged

Update all dependencies #510

merged 1 commit into from
Apr 1, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 1, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 18.15.6 -> 18.15.11 age adoption passing confidence
@typescript-eslint/eslint-plugin 5.56.0 -> 5.57.0 age adoption passing confidence
@typescript-eslint/parser 5.56.0 -> 5.57.0 age adoption passing confidence
esbuild 0.17.12 -> 0.17.14 age adoption passing confidence
eslint (source) 8.36.0 -> 8.37.0 age adoption passing confidence
prettier (source) 2.8.6 -> 2.8.7 age adoption passing confidence
sass 1.59.3 -> 1.60.0 age adoption passing confidence

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.57.0

Compare Source

Bug Fixes
  • eslint-plugin: [no-unnecessary-boolean-literal-compare] simplify fixer and add support for double negation (#​6620) (81c8519)
  • eslint-plugin: correct crashes with getTypeArguments for ts < 3.7 (#​6767) (59eab58)
Features
  • eslint-plugin: [consistent-type-assertions] add suggestions for objectLiteralTypeAssertions (#​6642) (720e811)
  • eslint-plugin: [consistent-type-assertions] autofix angle bracket assertions to as (#​6641) (ad8ea64)
  • eslint-plugin: add no-duplicate-type-constituents rule (#​5728) (bc31078)
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.57.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

evanw/esbuild

v0.17.14

Compare Source

  • Allow the TypeScript 5.0 const modifier in object type declarations (#​3021)

    The new TypeScript 5.0 const modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild:

    interface Foo { <const T>(): T }
    type Bar = { new <const T>(): T }
  • Implement preliminary lowering for CSS nesting (#​1945)

    Chrome has implemented the new CSS nesting specification in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform!

    This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the :is() pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support :is() (e.g. Chrome 88+). You'll need to set esbuild's target to the browsers you intend to support to tell esbuild to do this transformation. You will get a warning if you use CSS nesting syntax with a target which includes older browsers that don't support :is().

    The lowering transformation looks like this:

    /* Original input */
    a.btn {
      color: #&#8203;333;
      &:hover { color: #&#8203;444 }
      &:active { color: #&#8203;555 }
    }
    
    /* New output (with --target=chrome88) */
    a.btn {
      color: #&#8203;333;
    }
    a.btn:hover {
      color: #&#8203;444;
    }
    a.btn:active {
      color: #&#8203;555;
    }

    More complex cases may generate the :is() pseudo-class:

    /* Original input */
    div, p {
      .warning, .error {
        padding: 20px;
      }
    }
    
    /* New output (with --target=chrome88) */
    :is(div, p) :is(.warning, .error) {
      padding: 20px;
    }

    In addition, esbuild now has a special warning message for nested style rules that start with an identifier. This isn't allowed in CSS because the syntax would be ambiguous with the existing declaration syntax. The new warning message looks like this:

    ▲ [WARNING] A nested style rule cannot start with "p" because it looks like the start of a declaration [css-syntax-error]
    
        <stdin>:1:7:
          1 │ main { p { margin: auto } }
            │        ^
            ╵        :is(p)
    
      To start a nested style rule with an identifier, you need to wrap the identifier in ":is(...)" to
      prevent the rule from being parsed as a declaration.
    

    Keep in mind that the transformation in this release is a preliminary implementation. CSS has many features that interact in complex ways, and there may be some edge cases that don't work correctly yet.

  • Minification now removes unnecessary & CSS nesting selectors

    This release introduces the following CSS minification optimizations:

    /* Original input */
    a {
      font-weight: bold;
      & {
        color: blue;
      }
      & :hover {
        text-decoration: underline;
      }
    }
    
    /* Old output (with --minify) */
    a{font-weight:700;&{color:#&#8203;00f}& :hover{text-decoration:underline}}
    
    /* New output (with --minify) */
    a{font-weight:700;:hover{text-decoration:underline}color:#&#8203;00f}
  • Minification now removes duplicates from CSS selector lists

    This release introduces the following CSS minification optimization:

    /* Original input */
    div, div { color: red }
    
    /* Old output (with --minify) */
    div,div{color:red}
    
    /* New output (with --minify) */
    div{color:red}

v0.17.13

Compare Source

  • Work around an issue with NODE_PATH and Go's WebAssembly internals (#​3001)

    Go's WebAssembly implementation returns EINVAL instead of ENOTDIR when using the readdir syscall on a file. This messes up esbuild's implementation of node's module resolution algorithm since encountering ENOTDIR causes esbuild to continue its search (since it's a normal condition) while other encountering other errors causes esbuild to fail with an I/O error (since it's an unexpected condition). You can encounter this issue in practice if you use node's legacy NODE_PATH feature to tell esbuild to resolve node modules in a custom directory that was not installed by npm. This release works around this problem by converting EINVAL into ENOTDIR for the readdir syscall.

  • Fix a minification bug with CSS @layer rules that have parsing errors (#​3016)

    CSS at-rules require either a {} block or a semicolon at the end. Omitting both of these causes esbuild to treat the rule as an unknown at-rule. Previous releases of esbuild had a bug that incorrectly removed unknown at-rules without any children during minification if the at-rule token matched an at-rule that esbuild can handle. Specifically cssnano can generate @layer rules with parsing errors, and empty @layer rules cannot be removed because they have side effects (@layer didn't exist when esbuild's CSS support was added, so esbuild wasn't written to handle this). This release changes esbuild to no longer discard @layer rules with parsing errors when minifying (the rule @layer c has a parsing error):

    /* Original input */
    @&#8203;layer a {
      @&#8203;layer b {
        @&#8203;layer c
      }
    }
    
    /* Old output (with --minify) */
    @&#8203;layer a.b;
    
    /* New output (with --minify) */
    @&#8203;layer a.b.c;
  • Unterminated strings in CSS are no longer an error

    The CSS specification provides rules for handling parsing errors. One of those rules is that user agents must close strings upon reaching the end of a line (i.e., before an unescaped line feed, carriage return or form feed character), but then drop the construct (declaration or rule) in which the string was found. For example:

    p {
      color: green;
      font-family: 'Courier New Times
      color: red;
      color: green;
    }

    ...would be treated the same as:

    p { color: green; color: green; }

    ...because the second declaration (from font-family to the semicolon after color: red) is invalid and is dropped.

    Previously using this CSS with esbuild failed to build due to a syntax error, even though the code can be interpreted by a browser. With this release, the code now produces a warning instead of an error, and esbuild prints the invalid CSS such that it stays invalid in the output:

    /* esbuild's new non-minified output: */
    p {
      color: green;
      font-family: 'Courier New Times
      color: red;
      color: green;
    }
    /* esbuild's new minified output: */
    p{font-family:'Courier New Times
    color: red;color:green}
eslint/eslint

v8.37.0

Compare Source

Features

Bug Fixes

  • 619f3fd fix: correctly handle null default config in RuleTester (#​17023) (Brad Zacher)
  • 1fbf118 fix: getFirstToken/getLastToken on comment-only node (#​16889) (Francesco Trotta)
  • 129e252 fix: Fix typo in logical-assignment-operators rule description (#​17000) (Francesco Trotta)

Documentation

Chores

prettier/prettier

v2.8.7

Compare Source

diff

Allow multiple decorators on same getter/setter (#​14584 by @​fisker)
// Input
class A {
  @&#8203;decorator()
  get foo () {}
  
  @&#8203;decorator()
  set foo (value) {}
}

// Prettier 2.8.6
SyntaxError: Decorators cannot be applied to multiple get/set accessors of the same name. (5:3)
  3 |   get foo () {}
  4 |   
> 5 |   @&#8203;decorator()
    |   ^^^^^^^^^^^^
  6 |   set foo (value) {}
  7 | }

// Prettier 2.8.7
class A {
  @&#8203;decorator()
  get foo() {}

  @&#8203;decorator()
  set foo(value) {}
}
sass/dart-sass

v1.60.0

Compare Source

  • Add support for the pi, e, infinity, -infinity, and NaN constants in
    calculations. These will be interpreted as the corresponding numbers.

  • Add support for unknown constants in calculations. These will be interpreted
    as unquoted strings.

  • Serialize numbers with value infinity, -infinity, and NaN to calc()
    expressions rather than CSS-invalid identifiers. Numbers with complex units
    still can't be serialized.


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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.

@github-actions
Copy link

github-actions bot commented Apr 1, 2023

Unit Test Results

    1 files  ±0    20 suites  ±0   6s ⏱️ ±0s
131 tests ±0  131 ✔️ ±0  0 💤 ±0  0 ±0 
135 runs  ±0  135 ✔️ ±0  0 💤 ±0  0 ±0 

Results for commit 685a506. ± Comparison against base commit 2866ab9.

@github-actions
Copy link

github-actions bot commented Apr 1, 2023

Coverage report for commit: 685a506
File: coverage/clover.xml

Cover ┌─────────────────────────┐ Freq.
   0% │ ██░░░░░░░░░░░░░░░░░░░░░ │  4.5%
  10% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  20% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  30% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  40% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  50% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  60% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  70% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  80% │ ██░░░░░░░░░░░░░░░░░░░░░ │  4.5%
  90% │ █████████████░░░░░░░░░░ │ 31.8%
 100% │ ███████████████████████ │ 59.1%
      └─────────────────────────┘
 *Legend:* █ = Current Distribution 
Summary - Lines: 90.03% | Methods: 89.20% | Branchs: 75.07%
FilesLinesMethodsBranchs
scripts
   CampaignRenderer.ts90.91%96.15%78.57%
   CampaignStat.ts89.53%87.50%88.89%
   Chat.ts100.00%100.00%-
   CombatFlag.ts100.00%100.00%100.00%
   EncounterRenderer.ts77.33%100.00%62.86%
   Handlers.ts87.27%72.73%76.92%
   SetupHooks.ts---
   StatManager.ts89.47%100.00%33.33%
   enums.ts100.00%100.00%100.00%
scripts/Helpers
   Dates.ts100.00%100.00%-
   Gamemaster.ts100.00%100.00%100.00%
   Logger.ts100.00%100.00%100.00%
   Trans.ts100.00%100.00%-
scripts/parsers
   DND5e.ts100.00%100.00%100.00%
   MidiQol.ts100.00%100.00%88.24%
   PF2e.ts100.00%100.00%58.82%
   ReadySetRoll.ts94.44%100.00%57.14%
scripts/stats
   DND5eStat.ts100.00%100.00%100.00%
   MidiQolStat.ts100.00%100.00%100.00%
   PF2eStat.ts100.00%100.00%100.00%
   ReadySetRollStat.ts92.00%100.00%66.67%
   Stat.ts91.48%83.08%60.67%

🤖 comment via lucassabreu/comment-coverage-clover

@sonarcloud
Copy link

sonarcloud bot commented Apr 1, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@renovate renovate bot merged commit 6e8760b into main Apr 1, 2023
@renovate renovate bot deleted the renovate/all branch April 1, 2023 07:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants