Heapy / komok

Life and collaboration assistant.
https://heapy.io/projects/komok
GNU Affero General Public License v3.0
32 stars 0 forks source link

Bump the all group in /frontend with 7 updates #121

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 7 months ago

Bumps the all group in /frontend with 7 updates:

Package From To
@types/node 20.12.2 20.12.5
@types/react 18.2.73 18.2.74
@types/react-dom 18.2.23 18.2.24
css-loader 6.10.0 7.1.0
sass 1.72.0 1.74.1
style-loader 3.3.4 4.0.0
typescript 5.4.3 5.4.4

Updates @types/node from 20.12.2 to 20.12.5

Commits


Updates @types/react from 18.2.73 to 18.2.74

Commits


Updates @types/react-dom from 18.2.23 to 18.2.24

Commits


Updates css-loader from 6.10.0 to 7.1.0

Release notes

Sourced from css-loader's releases.

v7.1.0

7.1.0 (2024-04-08)

Features

  • added the getJSON option to output CSS modules mapping (#1577) (af834b4)

v7.0.0

7.0.0 (2024-04-04)

⚠ BREAKING CHANGES

  • The modules.namedExport option is true by default if you enable the esModule option

Migration guide:

Before:

import style from "./style.css";

console.log(style.myClass);

After:

import * as style from "./style.css";

console.log(style.myClass);

  • The modules.exportLocalsConvention has the value as-is when the modules.namedExport option is true and you don't specify a value
  • Minimum supported webpack version is 5.27.0
  • Minimum supported Node.js version is 18.12.0

Features

  • The modules.namedExports option works fine with any modules.exportLocalsConvention values (f96a110)
  • Added dashed variants for the modules.exportLocalsConvention options (40e1668)

v6.11.0

6.11.0 (2024-04-03)

Features

... (truncated)

Changelog

Sourced from css-loader's changelog.

7.1.0 (2024-04-08)

Features

  • added the getJSON option to output CSS modules mapping (#1577) (af834b4)

7.0.0 (2024-04-04)

⚠ BREAKING CHANGES

  • The modules.namedExport option is true by default if you enable the esModule option

Migration guide:

Before:

import style from "./style.css";

console.log(style.myClass);

After:

import * as style from "./style.css";

console.log(style.myClass);

To restore 6.x behavior, please use:

module.exports = {
  module: {
    rules: [
      {
        test: /\.css$/i,
        loader: "css-loader",
        options: {
          modules: {
            namedExport: false,
            exportLocalsConvention: 'as-is',
            //
            // or, if you prefer camelcase style
            //
            // exportLocalsConvention: 'camel-case-only'
          },
</tr></table> 

... (truncated)

Commits


Updates sass from 1.72.0 to 1.74.1

Release notes

Sourced from sass's releases.

Dart Sass 1.74.1

To install Sass 1.74.1, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

  • No user-visible changes.

See the full changelog for changes in earlier releases.

Changelog

Sourced from sass's changelog.

1.74.1

  • No user-visible changes.

1.74.0

JS API

  • Add a new top-level deprecations object, which contains various Deprecation objects that define the different types of deprecation used by the Sass compiler and can be passed to the options below.

  • Add a new fatalDeprecations compiler option that causes the compiler to error if any deprecation warnings of the provided types are encountered. You can also pass in a Version object to treat all deprecations that were active in that Dart Sass version as fatal.

  • Add a new futureDeprecations compiler option that allows you to opt-in to certain deprecations early (currently just import).

  • Add a new silenceDeprecations compiler option to ignore any deprecation warnings of the provided types.

Command-Line Interface

  • Add a new --silence-deprecation flag, which causes the compiler to ignore any deprecation warnings of the provided types.

  • Previously, if a future deprecation was passed to --fatal-deprecation but not --future-deprecation, it would be treated as fatal despite not being enabled. Both flags are now required to treat a future deprecation as fatal with a warning emitted if --fatal-deprecation is passed without --future-deprecation, matching the JS API's behavior.

Dart API

  • The compile methods now take in a silenceDeprecations parameter, which causes the compiler to ignore any deprecation warnings of the provided types.

  • Add Deprecation.obsoleteIn to match the JS API. This is currently null for all deprecations, but will be used once some deprecations become obsolete in Dart Sass 2.0.0.

  • Potentially breaking bug fix: Fix a bug where compileStringToResultAsync ignored fatalDeprecations and futureDeprecations.

  • The behavior around making future deprecations fatal mentioned in the CLI section above has also been changed in the Dart API.

1.73.0

... (truncated)

Commits


Updates style-loader from 3.3.4 to 4.0.0

Release notes

Sourced from style-loader's releases.

v4.0.0

4.0.0 (2024-04-08)

⚠ BREAKING CHANGES

  • minimum supported webpack version is 5.27.0
  • minimum support Node.js version is 18.12.0
  • the insert option can only be a selector or the path to the module

Migration:

Before:

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.css$/i,
        use: [
          {
            loader: "style-loader",
            options: {
              injectType: "styleTag",
              styleTagTransform: function (css, style) {
                // Do something ...
                style.innerHTML = `${css}.modify{}\n`;
            document.head.appendChild(style);
          },
        },
      },
      &quot;css-loader&quot;,
    ],
  },
],

}, };

After:

insert-function.js

function insert(css, style) {
  var parent = options.target || document.head;
</tr></table> 

... (truncated)

Changelog

Sourced from style-loader's changelog.

4.0.0 (2024-04-08)

⚠ BREAKING CHANGES

  • minimum supported webpack version is 5.27.0
  • minimum support Node.js version is 18.12.0
  • the insert option can only be a selector or the path to the module

Migration:

Before:

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.css$/i,
        use: [
          {
            loader: "style-loader",
            options: {
              injectType: "styleTag",
              styleTagTransform: function (css, style) {
                // Do something ...
                style.innerHTML = `${css}.modify{}\n`;
            document.head.appendChild(style);
          },
        },
      },
      &quot;css-loader&quot;,
    ],
  },
],

}, };

After:

insert-function.js

function insert(css, style) {
  var parent = options.target || document.head;

</tr></table>

... (truncated)

Commits
  • 091d37d chore(release): 4.0.0
  • abc0b5f docs: improve more
  • 565362c docs: update
  • 7122cde refactor!: the insert option can only be a selector or the path to the mo...
  • 11b8639 refactor!: the styleTagTransform option can only be the path to the module
  • 7ec1120 test: fix
  • 977bb71 refactor!: minimum supported webpack version is 5.27.0
  • a70555a test: update
  • dc6e368 refactor!: minimum support Node.js version is 18.12.0
  • b7cdc6c chore: update codecov-action to v4 (#623)
  • Additional commits viewable in compare view


Updates typescript from 5.4.3 to 5.4.4

Release notes

Sourced from typescript's releases.

TypeScript 5.4.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Commits
  • 8eb3367 Bump version to 5.4.4 and LKG
  • de9096b 🤖 Pick PR #57871 (Divide-and-conquer strategy for int...) into release-5.4 (#...
  • 06aae98 🤖 Pick PR #57973 (Compare package.json paths with cor...) into release-5.4 (#...
  • 6d8134e 🤖 Pick PR #57637 (Fixed a regression related to deter...) into release-5.4 (#...
  • 1c25c7f 🤖 Pick PR #57968 (Normalize slashes for paths in watc...) into release-5.4 (#...
  • 3caec2c Cherry pick PR 57887 into release-5.4 (#57898)
  • 896947e 🤖 Pick PR #57938 (Directories dont check modified tim...) into release-5.4 (#...
  • 521d3fb 🤖 Pick PR #57950 (Watch events enhancements) into release-5.4 (#57967)
  • See full diff in compare view


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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
github-actions[bot] commented 7 months ago

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report To be able to view the detailed Qodana report, you can either: 1. Register at [Qodana Cloud](https://qodana.cloud/) and [configure the action](https://github.com/jetbrains/qodana-action#qodana-cloud) 2. Use [GitHub Code Scanning with Qodana](https://github.com/jetbrains/qodana-action#github-code-scanning) 3. Host [Qodana report at GitHub Pages](https://github.com/JetBrains/qodana-action/blob/3a8e25f5caad8d8b01c1435f1ef7b19fe8b039a0/README.md#github-pages) 4. Inspect and use `qodana.sarif.json` (see [the Qodana SARIF format](https://www.jetbrains.com/help/qodana/qodana-sarif-output.html#Report+structure) for details) To get `*.log` files or any other Qodana artifacts, run the action with `upload-result` option set to `true`, so that the action will upload the files as the job artifacts: ```yaml - name: 'Qodana Scan' uses: JetBrains/qodana-action@v2023.3.2 with: upload-result: true ```
Contact Qodana team Contact us at [qodana-support@jetbrains.com](mailto:qodana-support@jetbrains.com) - Or via our issue tracker: https://jb.gg/qodana-issue - Or share your feedback: https://jb.gg/qodana-discussions