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.

Sign up for GitHub

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

Jump to bottom

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 16, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@biomejs/biome (source) 1.7.3 -> 1.8.3 age adoption passing confidence
@hono/node-server 1.11.1 -> 1.12.1 age adoption passing confidence
@swc/core (source) 1.5.7 -> 1.7.14 age adoption passing confidence
@types/react (source) 18.2.73 -> 18.3.4 age adoption passing confidence
@types/react-dom (source) 18.2.23 -> 18.3.0 age adoption passing confidence
@vitejs/plugin-react (source) 4.2.1 -> 4.3.1 age adoption passing confidence
autoprefixer 10.4.19 -> 10.4.20 age adoption passing confidence
hono (source) 4.3.7 -> 4.5.8 age adoption passing confidence
postcss (source) 8.4.38 -> 8.4.41 age adoption passing confidence
react (source) 18.3.0-canary-5bcade5fc-20231208 -> 18.3.1 age adoption passing confidence
react-dom (source) 18.3.0-canary-5bcade5fc-20231208 -> 18.3.1 age adoption passing confidence
react-server-dom-webpack (source) 18.3.0-canary-5bcade5fc-20231208 -> 18.3.0-next-fecc288b7-20221025 age adoption passing confidence
tailwindcss (source) 3.4.3 -> 3.4.10 age adoption passing confidence
vite (source) 5.2.11 -> 5.4.2 age adoption passing confidence
waku (source) 0.18.1 -> 0.21.0 age adoption passing confidence

Release Notes

biomejs/biome (@​biomejs/biome)

v1.8.3

Compare Source

CLI
Bug fixes

  • Fix #​3104 by suppressing node warnings when using biome migrate. Contributed by @​SuperchupuDev

  • Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#​3148). Contributed by @​Sec-ant

Parser
Bug fixes
Formatter
Bug fixes
Linter
New features
Bug fixes
  • useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #​3247. Contributed by @​Conaclos
  • Fixes #​3066 by taking into account the dependencies declared in the package.json. Contributed by @​ematipico
  • The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #​3292. Contributed by @​Sec-ant
Enhancements

  • Enhance tailwind sorting lint rule #​1274 with variant support.

    Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order.
    Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class.
    Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight).
    Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant.
    Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last.
    Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

    Contributed by @​lutaok

v1.8.2

Compare Source

CLI
Bug fixes
  • Fix #​3201 by correctly injecting the source code of the file when printing the diagnostics. Contributed by @​ematipico
  • Fix #​3179 where comma separators are not correctly removed after running biome migrate and thus choke the parser. Contributed by @​Sec-ant
  • Fix #​3232 by correctly using the colors set by the user. Contributed by @​ematipico
Enhancement

  • Reword the reporter message No fixes needed to No fixes applied.

    The former message is misleading when there're still errors or warnings in the files that should be taken care of manually. For example:

    Checked 2 files in <TIME>. No fixes needed.
Found 2 errors.

    The new message suits better in these cases.

    Contributed by @​Sec-ant

Configuration
Bug fixes

  • Don't conceal previous overrides (#​3176).

    Previously, each override inherited the unset configuration of the base configuration.
    This means that setting a configuration in an override can be concealed by a subsequent override that inherits of the value from the base configuration.

    For example, in the next example, noDebugger was disabled for the index.js file.

    {
  "linter": {
    "rules": {
      "suspicious": { "noDebugger": "off" }
    }
  },
  "overrides": [
    {
      "include": ["index.js"],
      "linter": {
        "rules": {
          "suspicious": { "noDebugger": "warn" }
        }
      }
    }, {
      "include": ["index.js"],
      "linter": {
        "rules": {
          "suspicious": { "noDoubleEquals": "off" }
        }
      }
    }
  ]
}

    The rule is now correctly enabled for the index.js file.

    Contributed by @​Conaclos

Formatter
Bug fixes
JavaScript APIs
Bug fixes
  • Fix a regression introduced by the release of v1.8.0
Linter
New features
Bug fixes

  • Add nursery/noShorthandPropertyOverrides. #​2958 Contributed by @​neokidev

  • Fix [#​3084] false positive by correctly recognize parenthesized return statement. Contributed by @​unvalley

  • useImportExtensions now suggests a correct fix for import '.' and import './.'. Contributed by @​minht11

  • Fix useDateNow false positive when new Date object has arguments new Date(0).getTime(). Contributed by @​minht11.

  • The noUnmatchableAnbSelector rule is now able to catch unmatchable an+b selectors like 0n+0 or -0n+0. Contributed by @​Sec-ant.

  • The useHookAtTopLevel rule now recognizes properties named as hooks like foo.useFoo(). Contributed by @​ksnyder9801

  • Fix #​3092, prevent warning for Custom properties (--*). Contributed by @​chansuke

  • Fix a false positive in the useLiteralKeys rule. (#​3160)

    This rule now ignores the following kind of computed member name:

    const a = {
  [`line1
  line2`]: true,
};

    Contributed by @​Sec-ant

  • The noUnknownProperty rule now ignores the composes property often used in css modules. #​3000 Contributed by @​chansuke

  • Fix false positives of the useExhaustiveDependencies rule.

    The component itself is considered stable when it is used recursively inside a hook closure defined inside of it:

    import { useMemo } from "react";

function MyRecursiveComponent() {
  // MyRecursiveComponent is stable, we don't need to add it to the dependencies list.
  const children = useMemo(() => <MyRecursiveComponent />, []);
  return <div>{children}</div>;
}

    Also, export default function and export default class are considered stable now because they can only appear at the top level of a module.

    Contributed by @​Sec-ant

  • Fix missing withDefaults macro in vue files for globals variables. Contributed by @​Shyam-Chen

Parser
Bug fixes

v1.8.1

Compare Source

Analyzer
CLI
Bug fixes
  • Fix #​3069, prevent overwriting paths when using --staged or --changed options. Contributed by @​unvalley
  • Fix a case where the file link inside a diagnostic wasn't correctly displayed inside a terminal run by VSCode. Contributed by @​uncenter
Configuration
Bug fixes
Editors
Formatter
Bug fixes
  • Fix the bug where whitespace after the & character in CSS nesting was incorrectly trimmed, ensuring proper targeting of child classes #​3061. Contributed by @​denbezrukov
  • Fix #​3068 where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by @​denbezrukov
  • Fix the formatting of CSS grid layout properties. Contributed by @​denbezrukov
JavaScript APIs
Linter
Bug fixes
Parser
New features
  • Implemented CSS Unknown At-Rule parsing, allowing the parser to gracefully handle unsupported or unrecognized CSS at-rules. Contributed by @​denbezrukov
Bug fixes
  • Fix #​3055 CSS: Layout using named grid lines is now correctly parsed. Contributed by @​denbezrukov
  • Fix #​3091. Allows the parser to handle nested style rules and at-rules properly, enhancing the parser's compatibility with the CSS Nesting Module. Contributed by @​denbezrukov

v1.8.0

Compare Source

Analyzer
New features
  • Allow suppression comments to suppress individual instances of rules. This is
    used for the lint rule useExhaustiveDependencies, which is now able to
    suppress specific dependencies. Fixes #​2509. Contributed by @​arendjr
Enhancements
  • Assume Astro object is always a global when processing .astro files. Contributed by @​minht11
  • Assume Vue compiler macros are globals when processing .vue files. (#​2771) Contributed by @​dyc3
CLI
New features

  • New clean command. Use this new command to clean after the biome-logs directory, and remove all the log files.

    biome clean

  • Add two new options --only and --skip to the command biome lint (#​58).

    The --only option allows you to run a given rule or rule group,
    For example, the following command runs only the style/useNamingConvention and style/noInferrableTypes rules.
    If the rule is disabled in the configuration, then its severity level is set to error for a recommended rule or warn otherwise.

    biome lint --only=style/useNamingConvention --only=style/noInferrableTypes

    Passing a group does not change the severity level of the rules in the group.
    All the disabled rules in the group will remain disabled.
    To ensure that the group is run, the recommended field of the group is enabled.
    The nursery group cannot be passed, as no rules are enabled by default in the nursery group.

    The --skip option allows you to skip the execution of a given group or a given rule.
    For example, the following command skips the style group and the suspicious/noExplicitAny rule.

    biome lint --skip=style --skip=suspicious/noExplicitAny

    You can also use --only and --skip together. --skip oevrrides --only.
    The following command executes only the rules from the style group, but the style/useNamingConvention rule.

    biome lint --only=style --skip=style/useNamingConvention

    These options are compatible with other options such as --write (previously --apply), and --reporter.

    Contributed by @​Conaclos

  • Add new command biome clean. Use this command to purge all the logs emitted by the Biome daemon. This command is really useful, because the Biome daemon tends
    log many files and contents during its lifecycle. This means that if your editor is open for hours (or even days), the biome-logs folder could become quite heavy. Contributed by @​ematipico

  • Add support for formatting and linting CSS files from the CLI. These operations are opt-in for the time being.

    If you don't have a configuration file, you can enable these features with --css-formatter-enabled and --css-linter-enabled:

    biome check --css-formatter-enabled=true --css-linter-enabled=true ./

    Contributed by @​ematipico

  • Add new CLI options to control the CSS formatting. Check the CLI reference page for more details. Contributed by @​ematipico

  • Add new options --write, --fix (alias of --write) and --unsafe to the command biome lint and biome check.
    Add a new option --fix (alias of --write) to the command biome format and biome migrate.

    biome <lint|check> --<write|fix> [--unsafe]
biome format --<write|fix>
biome migrate --<write|fix>

    The biome <lint|check> --<write|fix> has the same behavior as biome <lint|check> --apply.
    The biome <lint|check> --<write|fix> --unsafe has the same behavior as biome <lint|check> --apply-unsafe.
    The biome format --fix has the same behavior as biome format --write.
    The biome migrate --fix has the same behavior as biome migrate --write.

    This change allows these commands to write modifications in the same options.
    With this change, the --apply and --apply-unsafe options are deprecated.

    Contributed by @​unvalley

Enhancements

  • Biome now executes commands (lint, format, check and ci) on the working directory by default. #​2266 Contributed by @​unvalley

    - biome check .
+ biome check    # You can run the command without the path

  • biome migrate eslint now tries to convert ESLint ignore patterns into Biome ignore patterns.

    ESLint uses gitignore patterns.
    Biome now tries to convert these patterns into Biome ignore patterns.

    For example, the gitignore pattern /src is a relative path to the file in which it appears.
    Biome now recognizes this and translates this pattern to ./src.

    Contributed by @​Conaclos

  • biome migrate eslint now supports the eslintIgnore field in package.json.

    ESLint allows the use of package.json as an ESLint configuration file.
    ESLint supports two fields: eslintConfig and eslintIgnore.
    Biome only supported the former. It now supports both.

    Contributed by @​Conaclos

  • biome migrate eslint now propagates NodeJS errors to the user.

    This will help users to identify why Biome is unable to load some ESLint configurations.

    Contributed by @​Conaclos

  • Add a new --reporter called summary. This reporter will print diagnostics in a different way, based on the tools (formatter, linter, etc.) that are executed.
    Import sorting and formatter shows the name of the files that require formatting. Instead, the linter will group the number of rules triggered and the number of errors/warnings:

    Formatter ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to be formatted:
main.ts
index.ts

Organize Imports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to have their imports sorted:
main.ts
index.ts

Analyzer ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Some analyzer rules were triggered

Rule Name                                               Diagnostics
lint/suspicious/noImplicitAnyLet                        12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDoubleEquals                          8 (8 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noRedeclare                             12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDebugger                              20 (20 error(s), 0 warning(s), 0 info(s))

    Contributed by @​ematipico

  • biome ci now enforces printing the output using colours. If you were previously using --colors=force, you can remove it because it's automatically set. Contributed by @​ematipico

  • Add a new --reporter called github. This reporter will print diagnostics using GitHub workflow commands:

    ::error title=lint/suspicious/noDoubleEquals,file=main.ts,line=4,endLine=4,col=3,endColumn=5::Use === instead of ==
::error title=lint/suspicious/noDebugger,file=main.ts,line=6,endLine=6,col=1,endColumn=9::This is an unexpected use of the debugger statement.
::error title=lint/nursery/noEvolvingAny,file=main.ts,line=8,endLine=8,col=5,endColumn=6::This variable's type is not allowed to evolve implicitly, leading to potential any types.

    Contributed by @​ematipico

  • Add a new --reporter called junit. This reporter will print diagnostics using GitHub workflow commands:

    <?xml version="1.0" encoding="UTF-8"?>
<testsuites name="Biome" tests="16" failures="16" errors="20" time="<TIME>">
  <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
      <testcase name="org.biome.lint.suspicious.noDoubleEquals" line="4" column="3">
          <failure message="Use === instead of ==. == is only allowed when comparing against `null`">line 3, col 2, Use === instead of ==. == is only allowed when comparing against `null`</failure>
      </testcase>
  </testsuite>
  <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
      <testcase name="org.biome.lint.suspicious.noDebugger" line="6" column="1">
          <failure message="This is an unexpected use of the debugger statement.">line 5, col 0, This is an unexpected use of the debugger statement.</failure>
      </testcase>
  </testsuite>
  <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
      <testcase name="org.biome.lint.nursery.noEvolvingAny" line="8" column="5">
          <failure message="This variable&apos;s type is not allowed to evolve implicitly, leading to potential any types.">line 7, col 4, This variable&apos;s type is not allowed to evolve implicitly, leading to potential any types.</failure>
      </testcase>
  </testsuite>
</testsuites>

    Contributed by @​ematipico

Bug fixes
  • Fix #​3024, where running biome init would create biome.json even if biome.jsonc already exists. Contributed by @​minht11
Configuration
New features

  • Add an rule option fix to override the code fix kind of a rule (#​2882).

    A rule can provide a safe or an unsafe code action.
    You can now tune the kind of code actions thanks to the fix option.
    This rule option takes a value among:

    • none: the rule no longer emits code actions.
    • safe: the rule emits safe code action.
    • unsafe: the rule emits unsafe code action.

    The following configuration disables the code actions of noUnusedVariables, makes the emitted code actions of style/useConst and style/useTemplate unsafe and safe respectively.

    {
  "linter": {
    "rules": {
      "correctness": {
        "noUnusedVariables": {
          "level": "error",
          "fix": "none"
        },
        "style": {
          "useConst": {
            "level": "warn",
            "fix": "unsafe"
          },
          "useTemplate": {
            "level": "warn",
            "fix": "safe"
          }
        }
      }
    }
  }
}

    Contributed by @​Conaclos

  • Add option javascript.linter.enabled to control the linter for JavaScript (and its super languages) files. Contributed by @​ematipico

  • Add option json.linter.enabled to control the linter for JSON (and its super languages) files. Contributed by @​ematipico

  • Add option css.linter.enabled to control the linter for CSS (and its super languages) files. Contributed by @​ematipico

  • Add option css.formatter, to control the formatter options for CSS (and its super languages) files. Contributed by @​ematipico

  • You can now change the severity of lint rules down to "info". The "info" severity doesn't emit error codes, and it isn't affected by other options like --error-on-warnings:

    {
  "linter": {
    "rules": {
      "suspicious": {
        "noDebugger": "info"
      }
    }
  }
}

    Contributed by @​ematipico

Enhancements
  • The javascript.formatter.trailingComma option is deprecated and renamed to javascript.formatter.trailingCommas. The corresponding CLI option --trailing-comma is also deprecated and renamed to --trailing-commas. Details can be checked in #​2492. Contributed by @​Sec-ant
Bug fixes
  • Fix a bug where if the formatter was disabled at the language level, it could be erroneously enabled by an
    override that did not specify the formatter section #​2924. Contributed by @​dyc3
  • Fix #​2990, now Biome doesn't add a trailing comma when formatting biome.json. Contributed by @​dyc3
Editors
New features
  • Add support for LSP Workspaces
Enhancements
  • The LSP doesn't crash anymore when the configuration file contains errors. If the configuration contains errors, Biome now shows a pop-up to the user, and it will only parse files using the default configuration.
    Formatting and linting is disabled until the configuration file is fixed. Contributed by @​ematipico
Bug fixes
  • Fixes #​2781, by correctly computing the configuration to apply to a specific file. Contributed by @​ematipico
Formatter
Bug fixes
Linter
Promoted rules

New rules are incubated in the nursery group. Once stable, we promote them to a stable group. The following rules are promoted:

New features
Enhancements
Bug fixes

  • noUndeclaredVariables and noUnusedImports now correctly handle import namespaces (#​2796).

    Previously, Biome bound unqualified type to import namespaces.
    Import namespaces can only be used as qualified names in a type (ambient) context.

    // Unused import
import * as Ns1 from "";
// This doesn't reference the import namespace `Ns1`
type T1 = Ns1; // Undeclared variable `Ns1`

// Unused import
import type * as Ns2 from "";
// This doesn't reference the import namespace `Ns2`
type T2 = Ns2; // Undeclared variable `Ns2`

import type * as Ns3 from "";
// This references the import namespace because it is a qualified name.
type T3 = Ns3.Inner;
// This also references the import namespace.
export type { Ns3 }

    Contributed by @​Conaclos

  • noUndeclaredVariables now correctly handle ambient computed member names (#​2975).

    A constant can be imported as a type and used in a computed member name of a member signature.
    Previously, Biome was unable to bind the value imported as a type to the computed member name.

    import type { NAME } from "./constants.js";
type X = { [NAME]: number };

    Contributed by @​Conaclos

  • noUndeclaredVariables now ignores this in JSX components (#​2636).

    The rule no longer reports this as undeclared in following code.

    import { Component } from 'react';

export class MyComponent extends Component {
  render() {
    return <this.foo />
  }
}

    Contributed by @​printfn and @​Conaclos

  • useJsxKeyInIterable now handles more cases involving fragments. See the snippets below. Contributed by @​dyc3

// valid
[].map((item) => {
	return <>{item.condition ? <div key={item.id} /> : <div key={item.id}>foo</div>}</>;
});

// invalid
[].map((item) => {
	return <>{item.condition ? <div /> : <div>foo</div>}</>;
});
  • noExcessiveNestedTestSuites no longer erroneously alerts on describe calls that are not invoking the global describe function. #​2599 Contributed by @​dyc3
// now valid
z.object({})
  .describe('')
  .describe('')
  .describe('')
  .describe('')
  .describe('')
  .describe('');

  • noEmptyBlockStatements no longer reports empty constructors using typescript parameter properties. #​3005 Contributed by @​dyc3

  • noEmptyBlockStatements no longer reports empty private or protected constructors. Contributed by @​dyc3

  • noExportsInTest rule no longer treats files with in-source testing as test files https://github.com/biomejs/biome/issues/2859. Contributed by @​ah-yu

  • useSortedClasses now keeps leading and trailing spaces when applying the code action inside template literals:

    i Unsafe fix: Sort the classes.

  1 1 │   <>
  2   │ - → <div·class={`${variable}·px-2·foo·p-4·bar`}/>
    2 │ + → <div·class={`${variable}·foo·bar·p-4·px-2`}/>
  3 3 │   	<div class={`px-2 foo p-4 bar ${variable}`}/>
  4 4 │   </>

  • noUndeclaredDependencies is correctly triggered when running biome ci. Contributed by @​ematipico

  • noUnusedVariables no longer panics when a certain combination of characters is typed. Contributed by @​ematipico

  • noUndeclaredVariables no logger alerts on arguments object in a function scope. Contributed by @​ah-yu

Parser
Enhancements
  • lang="tsx" is now supported in Vue Single File Components. #​2765 Contributed by @​dyc3
Bug fixes

  • The const modifier for type parameters is now accepted for TypeScript new signatures (#​2825).

    The following code is now correctly parsed:

    interface I {
  new<const T>(x: T): T
}

    Contributed by @​Conaclos

  • Some invalid TypeScript syntax caused the Biome parser to crash.

    The following invalid syntax no longer causes the Biome parser to crash:

    declare using x: null;
declare qwait using x: null;

    Contributed by @​Conaclos

honojs/node-server (@​hono/node-server)

v1.12.1

Compare Source

What's Changed

Full Changelog: honojs/node-server@v1.12.0...v1.12.1

v1.12.0

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v1.11.5...v1.12.0

v1.11.5

Compare Source

What's Changed

Full Changelog: honojs/node-server@v1.11.4...v1.11.5

v1.11.4

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v1.11.3...v1.11.4

v1.11.3

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v1.11.2...v1.11.3

[v1.11.2](https://togithub.com/honojs/node-server/releases/t

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 was generated by Mend Renovate. View the repository job log.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Dec 16, 2023 •
edited

⚠️ No Changeset found

Latest commit: b5381dd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel Vercel
Copy link

vercel bot commented Dec 16, 2023 •
edited

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
waku-rsc-async-demo ❌ Failed (Inspect) Dec 16, 2023 2:49am

@sweep-ai Sweep AI
Copy link
Contributor

sweep-ai bot commented Dec 16, 2023

Apply Sweep Rules to your PR?

  • Apply: All new business logic should have corresponding unit tests.
  • Apply: Refactor large functions to be more modular.
  • Apply: Add docstrings to all functions and file headers.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from fbcc066 to 9844bf8 Compare December 16, 2023 07:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 83f1b13 to 332d808 Compare December 17, 2023 00:49
@renovate renovate bot changed the title fix(deps): update all non-major dependencies to v18.3.0-next-fecc288b7-20221025 fix(deps): update all non-major dependencies Dec 17, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e8d14a2 to aa674ce Compare December 17, 2023 16:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4511e60 to 8f14be7 Compare August 6, 2024 12:37
coderabbitai[bot]
coderabbitai bot reviewed Aug 6, 2024
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4511e60 and 8f14be7.

Files ignored due to path filters (1)
  • bun.lockb is excluded by !**/bun.lockb
Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • package.json

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from c625811 to c2b9e4c Compare August 7, 2024 18:51
@socket-security Socket Security
Copy link

socket-security bot commented Aug 7, 2024 •
edited

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@biomejs/biome@1.8.3 shell +8 191 MB dominionl
npm/@hono/node-server@1.12.1 network 0 162 kB yusukebe
npm/@swc/core@1.7.14 None +12 445 MB kdy1, kwonoj
npm/@types/react-dom@18.3.0 None 0 37.8 kB types
npm/@types/react@18.3.4 None +2 1.69 MB types
npm/@vitejs/plugin-react@4.3.1 Transitive: environment, filesystem, shell, unsafe +57 11.7 MB vitebot
npm/autoprefixer@10.4.20 environment Transitive: filesystem, shell +10 2.7 MB ai
npm/hono@4.5.8 None 0 1.01 MB yusukebe
npm/postcss@8.4.41 environment, filesystem +3 368 kB ai
npm/react-dom@18.3.1 environment +3 4.63 MB react-bot
npm/react-server-dom-webpack@18.3.0-next-fecc288b7-20221025 Transitive: environment, eval, filesystem, network, shell, unsafe +84 25.7 MB acdlite
npm/react@18.3.1 environment +2 339 kB react-bot
npm/tailwindcss@3.4.10 environment, filesystem Transitive: network, shell, unsafe +103 15.1 MB adamwathan
npm/vite@5.4.2 Transitive: environment, eval, filesystem, network, shell +56 277 MB antfu, patak, soda, ...2 more
npm/waku@0.21.0 Transitive: environment, eval, filesystem, network, shell, unsafe +142 739 MB daishi

🚮 Removed packages: npm/@biomejs/biome@1.7.3), npm/@hono/node-server@1.11.1), npm/@swc/core@1.5.7), npm/@types/react-dom@18.2.23), npm/@types/react@18.2.73), npm/@vitejs/plugin-react@4.2.1), npm/autoprefixer@10.4.19), npm/hono@4.3.7), npm/postcss@8.4.38), npm/react-dom@18.3.0-canary-5bcade5fc-20231208), npm/react-server-dom-webpack@18.3.0-canary-5bcade5fc-20231208), npm/react@18.3.0-canary-5bcade5fc-20231208), npm/tailwindcss@3.4.3), npm/vite@5.2.11), npm/waku@0.18.1)

View full report↗︎

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 3a0c2af to 470a264 Compare August 9, 2024 17:09
coderabbitai[bot]
coderabbitai bot reviewed Aug 9, 2024
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (1)
package.json (1)

21-21: Breaking Changes Detected in waku Update

The waku library has undergone several breaking changes in its recent updates. Here are some of the notable changes:

  • No index HTML (#289)
  • Switch to full SSR from RSC-only SSR (#147)
  • Multiple elements in a single response (#124)
  • src and dist folders at the same level (#92)

These changes may impact your project, especially if you rely on SSR or specific directory structures. Please review these changes and test your application to ensure compatibility.

Analysis chain

Verify compatibility of waku update.

The update from 0.18.1 to 0.20.2 may introduce new features or changes in functionality. Ensure that the changes are compatible with your existing codebase.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of `waku` update.

# Test: Check for breaking changes in the changelog or release notes.
gh release view waku --repo status-im/js-waku --json body --jq '.body' | grep -i "breaking"

Length of output: 107

Script:

#!/bin/bash
# Search for the `waku` package repository or related information in the codebase.
rg "waku" package.json -A 5

Length of output: 621

Script:

#!/bin/bash
# Search for mentions of `waku` in README or documentation files to find more information.
rg "waku" README.md -A 5

Length of output: 1229

Script:

#!/bin/bash
# Fetch release notes from the `dai-shi/waku` repository to check for breaking changes.
gh release view --repo dai-shi/waku --json body --jq '.body' | grep -i "breaking"

Length of output: 97

Script:

#!/bin/bash
# Search for a changelog or similar file in the `dai-shi/waku` repository for update information.
gh repo clone dai-shi/waku waku-repo
cd waku-repo
fd -e md -e txt --exec rg -i "breaking" {}

Length of output: 922

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8f14be7 and 470a264.

Files ignored due to path filters (1)
  • bun.lockb is excluded by !**/bun.lockb
Files selected for processing (1)
  • package.json (1 hunks)
Additional comments not posted (14)
package.json (14)

33-33: Verify compatibility of vite update.

The update from 5.2.11 to 5.4.0 may include performance optimizations or new features. Ensure that the changes are compatible with your development environment.

20-20: Verify compatibility of react-server-dom-webpack update.

The update from 18.3.0-canary-5bcade5fc-20231208 to 18.3.0-next-fecc288b7-20221025 reflects a shift in the release channel. Ensure that the update does not introduce breaking changes in your application.

24-24: Verify compatibility of @biomejs/biome update.

The update from 1.7.3 to 1.8.3 may include improvements or changes in functionality. Ensure that the changes are compatible with your development environment.

25-25: Verify compatibility of @swc/core update.

The update from 1.5.7 to 1.7.9 may include performance optimizations or new features. Ensure that the changes are compatible with your development environment.

30-30: Verify compatibility of postcss update.

The update from 8.4.38 to 8.4.41 likely includes minor fixes or improvements. Ensure that the changes are compatible with your development environment.

19-19: Verify compatibility of react-dom update.

The update from 18.3.0-canary-5bcade5fc-20231208 to 18.3.1 likely includes stability improvements. Ensure that the update does not introduce breaking changes in your application.

29-29: Verify compatibility of autoprefixer update.

The update from 10.4.19 to 10.4.20 likely includes minor fixes or improvements. Ensure that the changes are compatible with your development environment.

18-18: Verify compatibility of react update.

The update from 18.3.0-canary-5bcade5fc-20231208 to 18.3.1 likely includes stability improvements. Ensure that the update does not introduce breaking changes in your application.

27-27: Verify compatibility of @types/react-dom update.

The update from 18.2.23 to 18.3.0 likely includes improvements or changes in type definitions. Ensure that the changes are compatible with your development environment.

26-26: Verify compatibility of @types/react update.

The update from 18.2.73 to 18.3.3 likely includes improvements or changes in type definitions. Ensure that the changes are compatible with your development environment.

17-17: Verify compatibility of hono update.

The update from 4.3.7 to 4.5.4 may include enhancements or bug fixes. Ensure that these changes are compatible with your current project setup.

31-31: Verify compatibility of tailwindcss update.

The update from 3.4.3 to 3.4.9 may include enhancements or bug fixes. Ensure that the changes are compatible with your development environment.

28-28: Verify compatibility of @vitejs/plugin-react update.

The update from 4.2.1 to 4.3.1 may include performance optimizations or new features. Ensure that the changes are compatible with your development environment.

15-15: Verify compatibility of @hono/node-server update.

The update from 1.11.1 to 1.12.0 may introduce new features or fixes. Ensure that the changes are compatible with your existing codebase and do not introduce breaking changes.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 470a264 to 572995d Compare August 9, 2024 21:46
coderabbitai[bot]
coderabbitai bot reviewed Aug 9, 2024
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 470a264 and 572995d.

Files ignored due to path filters (1)
  • bun.lockb is excluded by !**/bun.lockb
Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • package.json

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 572995d to 44a9a4a Compare August 11, 2024 08:03
coderabbitai[bot]
coderabbitai bot reviewed Aug 11, 2024
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 572995d and 44a9a4a.

Files ignored due to path filters (1)
  • bun.lockb is excluded by !**/bun.lockb
Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • package.json

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 43cb130 to b6ca021 Compare August 17, 2024 11:32
coderabbitai[bot]
coderabbitai bot reviewed Aug 17, 2024
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 44a9a4a and b6ca021.

Files ignored due to path filters (1)
  • bun.lockb is excluded by !**/bun.lockb
Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • package.json

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b6ca021 to 03a0fa1 Compare August 19, 2024 01:28
coderabbitai[bot]
coderabbitai bot reviewed Aug 19, 2024
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b6ca021 and 03a0fa1.

Files ignored due to path filters (1)
  • bun.lockb is excluded by !**/bun.lockb
Files selected for processing (1)
  • package.json (1 hunks)
Additional comments not posted (15)
package.json (15)

17-17: Verify compatibility with hono v4.5.6.

Ensure that the update from 4.3.7 to 4.5.6 does not introduce breaking changes. Check the release notes for any significant updates.

19-19: Verify compatibility with react-dom v18.3.1.

Ensure that the update from 18.3.0-canary-5bcade5fc-20231208 to 18.3.1 does not introduce breaking changes. Check the release notes for any significant updates.

18-18: Verify compatibility with react v18.3.1.

Ensure that the update from 18.3.0-canary-5bcade5fc-20231208 to 18.3.1 does not introduce breaking changes. Check the release notes for any significant updates.

31-31: Verify compatibility with tailwindcss v3.4.10.

Ensure that the update from 3.4.3 to 3.4.10 does not introduce breaking changes. Check the release notes for any significant updates.

27-27: Verify compatibility with @types/react-dom v18.3.0.

Ensure that the update from 18.2.23 to 18.3.0 does not introduce breaking changes. Check the release notes for any significant updates.

20-20: Verify compatibility with react-server-dom-webpack v18.3.0-next-fecc288b7-20221025.

Ensure that the update from 18.3.0-canary-5bcade5fc-20231208 to 18.3.0-next-fecc288b7-20221025 does not introduce breaking changes. Check the release notes for any significant updates.

24-24: Verify compatibility with @biomejs/biome v1.8.3.

Ensure that the update from 1.7.3 to 1.8.3 does not introduce breaking changes. Check the release notes for any significant updates.

30-30: Verify compatibility with postcss v8.4.41.

Ensure that the update from 8.4.38 to 8.4.41 does not introduce breaking changes. Check the release notes for any significant updates.

26-26: Verify compatibility with @types/react v18.3.3.

Ensure that the update from 18.2.73 to 18.3.3 does not introduce breaking changes. Check the release notes for any significant updates.

21-21: Verify compatibility with waku v0.20.2.

Ensure that the update from 0.18.1 to 0.20.2 does not introduce breaking changes. Check the release notes for any significant updates.

25-25: Verify compatibility with @swc/core v1.7.11.

Ensure that the update from 1.5.7 to 1.7.11 does not introduce breaking changes. Check the release notes for any significant updates.

29-29: Verify compatibility with autoprefixer v10.4.20.

Ensure that the update from 10.4.19 to 10.4.20 does not introduce breaking changes. Check the release notes for any significant updates.

15-15: Verify compatibility with @hono/node-server v1.12.1.

Ensure that the update from 1.11.1 to 1.12.1 does not introduce breaking changes. Check the release notes for any significant updates.

33-33: Verify compatibility with vite v5.4.1.

Ensure that the update from 5.2.11 to 5.4.1 does not introduce breaking changes. Check the release notes for any significant updates.

28-28: Verify compatibility with @vitejs/plugin-react v4.3.1.

Ensure that the update from 4.2.1 to 4.3.1 does not introduce breaking changes. Check the release notes for any significant updates.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 9a4a6a0 to 759acf1 Compare August 20, 2024 21:53
coderabbitai[bot]
coderabbitai bot reviewed Aug 20, 2024
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 03a0fa1 and 759acf1.

Files ignored due to path filters (1)
  • bun.lockb is excluded by !**/bun.lockb
Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • package.json

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 759acf1 to 194eddc Compare August 21, 2024 03:26
coderabbitai[bot]
coderabbitai bot reviewed Aug 21, 2024
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 759acf1 and 194eddc.

Files ignored due to path filters (1)
  • bun.lockb is excluded by !**/bun.lockb
Files selected for processing (1)
  • package.json (1 hunks)
Additional comments not posted (15)
package.json (15)

15-15: Verify compatibility for @hono/node-server.

The update from 1.11.1 to 1.12.1 is a minor version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for @hono/node-server to confirm compatibility.

17-17: Verify compatibility for hono.

The update from 4.3.7 to 4.5.7 is a minor version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for hono to confirm compatibility.

18-18: Verify compatibility for react.

The update from a canary version to a stable release (18.3.1) should improve stability. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for react to confirm compatibility.

19-19: Verify compatibility for react-dom.

The update from a canary version to a stable release (18.3.1) should improve stability. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for react-dom to confirm compatibility.

20-20: Verify compatibility for react-server-dom-webpack.

The update changes the release channel, which might introduce new features or changes. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for react-server-dom-webpack to confirm compatibility.

21-21: Verify compatibility for waku.

The update from 0.18.1 to 0.21.0 is a minor version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for waku to confirm compatibility.

24-24: Verify compatibility for @biomejs/biome.

The update from 1.7.3 to 1.8.3 is a minor version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for @biomejs/biome to confirm compatibility.

25-25: Verify compatibility for @swc/core.

The update from 1.5.7 to 1.7.14 is a minor version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for @swc/core to confirm compatibility.

26-26: Verify compatibility for @types/react.

The update from 18.2.73 to 18.3.4 is a minor version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for @types/react to confirm compatibility.

27-27: Verify compatibility for @types/react-dom.

The update from 18.2.23 to 18.3.0 is a minor version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for @types/react-dom to confirm compatibility.

28-28: Verify compatibility for @vitejs/plugin-react.

The update from 4.2.1 to 4.3.1 is a minor version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for @vitejs/plugin-react to confirm compatibility.

29-29: Verify compatibility for autoprefixer.

The update from 10.4.19 to 10.4.20 is a patch version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for autoprefixer to confirm compatibility.

30-30: Verify compatibility for postcss.

The update from 8.4.38 to 8.4.41 is a patch version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for postcss to confirm compatibility.

31-31: Verify compatibility for tailwindcss.

The update from 3.4.3 to 3.4.10 is a patch version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for tailwindcss to confirm compatibility.

33-33: Verify compatibility for vite.

The update from 5.2.11 to 5.4.2 is a minor version change. Ensure that there are no breaking changes and that the new features are compatible with the existing codebase.

Review the release notes for vite to confirm compatibility.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 194eddc to b5381dd Compare August 22, 2024 07:17
coderabbitai[bot]
coderabbitai bot reviewed Aug 22, 2024
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 194eddc and b5381dd.

Files ignored due to path filters (1)
  • bun.lockb is excluded by !**/bun.lockb
Files selected for processing (1)
  • package.json (1 hunks)
Additional comments not posted (15)
package.json (15)

15-15: Verify compatibility for @hono/node-server update.

The version has been updated from 1.11.1 to 1.12.1. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

17-17: Verify compatibility for hono update.

The version has been updated from 4.3.7 to 4.5.8. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

18-18: Verify compatibility for react update.

The version has been updated from 18.3.0-canary-5bcade5fc-20231208 to 18.3.1. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

19-19: Verify compatibility for react-dom update.

The version has been updated from 18.3.0-canary-5bcade5fc-20231208 to 18.3.1. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

20-20: Verify compatibility for react-server-dom-webpack update.

The version has been updated from 18.3.0-canary-5bcade5fc-20231208 to 18.3.0-next-fecc288b7-20221025. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

21-21: Verify compatibility for waku update.

The version has been updated from 0.18.1 to 0.21.0. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

24-24: Verify compatibility for @biomejs/biome update.

The version has been updated from 1.7.3 to 1.8.3. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

25-25: Verify compatibility for @swc/core update.

The version has been updated from 1.5.7 to 1.7.14. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

26-26: Verify compatibility for @types/react update.

The version has been updated from 18.2.73 to 18.3.4. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

27-27: Verify compatibility for @types/react-dom update.

The version has been updated from 18.2.23 to 18.3.0. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

28-28: Verify compatibility for @vitejs/plugin-react update.

The version has been updated from 4.2.1 to 4.3.1. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

29-29: Verify compatibility for autoprefixer update.

The version has been updated from 10.4.19 to 10.4.20. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

30-30: Verify compatibility for postcss update.

The version has been updated from 8.4.38 to 8.4.41. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

31-31: Verify compatibility for tailwindcss update.

The version has been updated from 3.4.3 to 3.4.10. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

33-33: Verify compatibility for vite update.

The version has been updated from 5.2.11 to 5.4.2. Ensure that the updated package is compatible with the rest of the codebase and does not introduce breaking changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@coderabbitai coderabbitai coderabbitai left review comments

@renovate-approve renovate-approve renovate-approve approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants