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): bump the minor-and-patch-updates group with 7 updates #112

Merged
merged 1 commit into from
Jun 10, 2024
Merged

chore(deps): bump the minor-and-patch-updates group with 7 updates #112

merged 1 commit into from
Jun 10, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 10, 2024

Bumps the minor-and-patch-updates group with 7 updates:

Package From To
type-fest 4.18.3 4.20.0
@biomejs/biome 1.7.3 1.8.0
@types/node 20.14.0 20.14.2
esbuild 0.21.4 0.21.5
prettier 3.3.0 3.3.1
tsx 4.11.1 4.15.1
vite 5.2.12 5.2.13

Updates type-fest from 4.18.3 to 4.20.0

Release notes

Sourced from type-fest's releases.

v4.20.0

  • SimplifyDeep: Support array (#888) a6ab051
  • IsLiteral: Return false for tagged types (#886) 587380c

sindresorhus/type-fest@v4.19.0...v4.20.0

v4.19.0

sindresorhus/type-fest@v4.18.3...v4.19.0

Commits

Updates @biomejs/biome from 1.7.3 to 1.8.0

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.8.0

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.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

1.8.0 (2024-06-04)

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.

... (truncated)

Commits
  • 378c05e release: v1.8.0 (#3033)
  • 44b5c29 refactor(noEvolvingAny): rename into noEvolvingTypes (#2959)
  • bc30892 feat(noUnusedFunctionParameters): add lint for unused function parameters, in...
  • 9a7d790 feat: add noLabelWithoutControl rule (#2987)
  • 21e2512 feat: allow "info" severity for analyzer rules (#3014)
  • f793b72 feat(linter): implement useDateNow (#2925)
  • e52084a feat(css_parser): add parsing css modules @​value at rule (#2985)
  • fec262f feat(linter): implement useErrorMessage (#2978)
  • b3da3ae refactor(migrate/eslint): improve naming-convention migration (#2968)
  • 125f34b ci: fix nightly version and restore update of manifest (#2953)
  • Additional commits viewable in compare view

Updates @types/node from 20.14.0 to 20.14.2

Commits

Updates esbuild from 0.21.4 to 0.21.5

Release notes

Sourced from esbuild's releases.

v0.21.5

  • Fix Symbol.metadata on classes without a class decorator (#3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }

  • Support import attributes with glob-style imports (#3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data

    example.ts:2:28:
  2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.5

  • Fix Symbol.metadata on classes without a class decorator (#3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }

  • Support import attributes with glob-style imports (#3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data

    example.ts:2:28:
  2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Commits

Updates prettier from 3.3.0 to 3.3.1

Release notes

Sourced from prettier's releases.

3.3.1

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.3.1

diff

Preserve empty lines in front matter (#16347 by @​fisker)

<!-- Input -->
---
foo:
  - bar1


bar2


bar3



Markdown
<!-- Prettier 3.3.0 -->

foo:

bar1
bar2
bar3


Markdown
<!-- Prettier 3.3.1 -->
foo:


bar1


bar2


bar3



Markdown

Preserve explicit language in front matter (#16348 by @​fisker)

<!-- Input -->
---yaml
</tr></table>

... (truncated)

Commits

Updates tsx from 4.11.1 to 4.15.1

Release notes

Sourced from tsx's releases.

v4.15.1

4.15.1 (2024-06-09)

Bug Fixes

  • prevent ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE (fb247eb)

This release is also available on:

v4.15.0

4.15.0 (2024-06-09)

Features

This release is also available on:

v4.14.1

4.14.1 (2024-06-08)

Bug Fixes

  • cjs: only hide transformers when namespaced (9e647a5)

This release is also available on:

v4.14.0

4.14.0 (2024-06-08)

... (truncated)

Commits
  • fb247eb fix: prevent ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE
  • c67d746 feat: esbuild 0.21.4
  • edbdfdf feat: esbuild 0.21.3
  • 6f1d305 feat: esbuild 0.21 (#19)
  • bbbf1a7 refactor(cjs): organize resolver logic
  • 9e647a5 fix(cjs): only hide transformers when namespaced
  • 4503421 feat: resolve .js → .ts in package.json exports & main
  • c35dbaa chore: add note about esm cjs interop optimization
  • 807f467 fix(esm): cjs interop to support decorators
  • 02d3856 fix(cjs): resolve directory import relative to parent (#42)
  • Additional commits viewable in compare view

Updates vite from 5.2.12 to 5.2.13

Changelog

Sourced from vite's changelog.

5.2.13 (2024-06-07)

Commits

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
chore(deps): bump the minor-and-patch-updates group with 7 updates
212cee4 
Bumps the minor-and-patch-updates group with 7 updates:

| Package | From | To |
| --- | --- | --- |
| [type-fest](https://github.com/sindresorhus/type-fest) | `4.18.3` | `4.20.0` |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `1.7.3` | `1.8.0` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `20.14.0` | `20.14.2` |
| [esbuild](https://github.com/evanw/esbuild) | `0.21.4` | `0.21.5` |
| [prettier](https://github.com/prettier/prettier) | `3.3.0` | `3.3.1` |
| [tsx](https://github.com/privatenumber/tsx) | `4.11.1` | `4.15.1` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `5.2.12` | `5.2.13` |


Updates `type-fest` from 4.18.3 to 4.20.0
- [Release notes](https://github.com/sindresorhus/type-fest/releases)
- [Commits](sindresorhus/type-fest@v4.18.3...v4.20.0)

Updates `@biomejs/biome` from 1.7.3 to 1.8.0
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/CHANGELOG.md)
- [Commits](https://github.com/biomejs/biome/commits/cli/v1.8.0/packages/@biomejs/biome)

Updates `@types/node` from 20.14.0 to 20.14.2
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `esbuild` from 0.21.4 to 0.21.5
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.21.4...v0.21.5)

Updates `prettier` from 3.3.0 to 3.3.1
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.3.0...3.3.1)

Updates `tsx` from 4.11.1 to 4.15.1
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.11.1...v4.15.1)

Updates `vite` from 5.2.12 to 5.2.13
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.2.13/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.2.13/packages/vite)

---
updated-dependencies:
- dependency-name: type-fest
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch-updates
- dependency-name: "@biomejs/biome"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch-updates
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch-updates
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch-updates
- dependency-name: prettier
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch-updates
- dependency-name: tsx
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch-updates
- dependency-name: vite
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch-updates
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jun 10, 2024
@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Jun 10, 2024

⚠️ No Changeset found

Latest commit: 212cee4

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Jun 10, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot merged commit 1c5b658 into main Jun 10, 2024
2 of 3 checks passed
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/minor-and-patch-updates-cb7c98142c branch June 10, 2024 04:02
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
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants