Skip to content

build(deps-dev): bump all - #1287

Merged
renovate[bot] merged 1 commit into
livefrom
renovate/all
Jun 20, 2024
Merged

build(deps-dev): bump all#1287
renovate[bot] merged 1 commit into
livefrom
renovate/all

Conversation

@renovate

@renovate renovate Bot commented Jun 20, 2024 •
edited
Loading

Copy link
Copy Markdown
Contributor

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@biomejs/biome (source) 1.8.1 -> 1.8.2 age adoption passing confidence devDependencies patch
@types/node (source) 20.14.5 -> 20.14.7 age adoption passing confidence devDependencies patch
cssnano 7.0.2 -> 7.0.3 age adoption passing confidence devDependencies patch
node (source) 20.14.0 -> 20.15.0 age adoption passing confidence engines minor
typescript (source) 5.4.5 -> 5.5.2 age adoption passing confidence devDependencies minor
unified (source) 11.0.4 -> 11.0.5 age adoption passing confidence devDependencies patch

Release Notes

biomejs/biome (@​biomejs/biome)

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
cssnano/cssnano (cssnano)

v7.0.3: v7.0.3

Compare Source

Bug Fixes

  • cssnano-preset-default: preserve SVG viewbox and title by default
  • postcss-convert-values: preserve percent sign in arguments of color functions when needed
  • postcss-ordered-values: preserve correct order in animation property
  • postcss-minify-selectors: preserve quotes when escaping selector is required
  • postcss-discard-comments: do not remove strings that only look like comments in selectors

Thanks to @​ota-meshi and @​seiyab for their contributions to this release.

nodejs/node (node)

v20.15.0: 2024-06-20, Version 20.15.0 'Iron' (LTS), @​marco-ippolito

Compare Source

test_runner: support test plans

It is now possible to count the number of assertions and subtests that are expected to run within a test. If the number of assertions and subtests that run does not match the expected count, the test will fail.

test('top level test', (t) => {
  t.plan(2);
  t.assert.ok('some relevant assertion here');
  t.subtest('subtest', () => {});
});

Contributed by Colin Ihrig in #​52860

inspector: introduce the --inspect-wait flag

This release introduces the --inspect-wait flag, which allows debugger to wait for attachement. This flag is useful when you want to debug the code from the beginning. Unlike --inspect-brk, which breaks on the first line, this flag waits for debugger to be connected and then runs the code as soon as a session is established.

Contributed by Kohei Ueno in #​52734

zlib: expose zlib.crc32()

This release exposes the crc32() function from zlib to user-land.

It computes a 32-bit Cyclic Redundancy Check checksum of data. If
value is specified, it is used as the starting value of the checksum,
otherwise, 0 is used as the starting value.

The CRC algorithm is designed to compute checksums and to detect error
in data transmission. It's not suitable for cryptographic authentication.

const zlib = require('node:zlib');
const { Buffer } = require('node:buffer');

let crc = zlib.crc32('hello');  // 907060870
crc = zlib.crc32('world', crc);  // 4192936109

crc = zlib.crc32(Buffer.from('hello', 'utf16le'));  // 1427272415
crc = zlib.crc32(Buffer.from('world', 'utf16le'), crc);  // 4150509955

Contributed by Joyee Cheung in #​52692

cli: allow running wasm in limited vmem with --disable-wasm-trap-handler

By default, Node.js enables trap-handler-based WebAssembly bound
checks. As a result, V8 does not need to insert inline bound checks
int the code compiled from WebAssembly which may speedup WebAssembly
execution significantly, but this optimization requires allocating
a big virtual memory cage (currently 10GB). If the Node.js process
does not have access to a large enough virtual memory address space
due to system configurations or hardware limitations, users won't
be able to run any WebAssembly that involves allocation in this
virtual memory cage and will see an out-of-memory error.

$ ulimit -v 5000000
$ node -p "new WebAssembly.Memory({ initial: 10, maximum: 100 });"
[eval]:1
new WebAssembly.Memory({ initial: 10, maximum: 100 });
^

RangeError: WebAssembly.Memory(): could not allocate memory
    at [eval]:1:1
    at runScriptInThisContext (node:internal/vm:209:10)
    at node:internal/process/execution:118:14
    at [eval]-wrapper:6:24
    at runScript (node:internal/process/execution:101:62)
    at evalScript (node:internal/process/execution:136:3)
    at node:internal/main/eval_string:49:3

--disable-wasm-trap-handler disables this optimization so that
users can at least run WebAssembly (with a less optimial performance)
when the virtual memory address space available to their Node.js
process is lower than what the V8 WebAssembly memory cage needs.

Contributed by Joyee Cheung in #​52766

Other Notable Changes
Commits
Microsoft/TypeScript (typescript)

v5.5.2

Compare Source

unifiedjs/unified (unified)

v11.0.5

Compare Source

Fix

Full Changelog: unifiedjs/unified@11.0.4...11.0.5

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (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.

@renovate renovate Bot added build labels Jun 20, 2024
@netlify

netlify Bot commented Jun 20, 2024 •
edited
Loading

Copy link
Copy Markdown

❌ Deploy Preview for gh-pages-openinf failed.

Name Link
🔨 Latest commit 54752e4
🔍 Latest deploy log https://app.netlify.com/sites/gh-pages-openinf/deploys/667496f4e477b4000840cc52

@socket-security

socket-security Bot commented Jun 20, 2024 •
edited
Loading

Copy link
Copy Markdown

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

Package New capabilities Transitives Size Publisher
npm/@biomejs/biome@1.8.2 None 0 0 B
npm/@types/node@20.14.7 None 0 0 B
npm/cssnano@7.0.3 Transitive: environment, filesystem, shell, unsafe +53 7.4 MB ludovicofischer
npm/typescript@5.5.2 None 0 0 B
npm/unified@11.0.5 None +8 274 kB wooorm

🚮 Removed packages: npm/cssnano@7.0.2, npm/typescript@5.4.5, npm/unified@11.0.4

View full report↗︎

@renovate
build(deps-dev): bump all
9d971e0 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
renovate Bot merged commit 5ef93d2 into live Jun 20, 2024
@renovate
renovate Bot deleted the renovate/all branch June 20, 2024 21:17
@DerekNonGeneric DerekNonGeneric added 🏗️ Category: Build Issues and PRs related to the build directory 📦 Type: Dependencies PRs that modify packages req'd by product in production 📦 Type: Developer Dependencies PRs that modify packages only req'd for local development and testing labels Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

🏗️ Category: Build Issues and PRs related to the build directory 📦 Type: Dependencies PRs that modify packages req'd by product in production 📦 Type: Developer Dependencies PRs that modify packages only req'd for local development and testing

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@DerekNonGeneric