Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(dev-deps): update dependency @ivangabriele/tsconfig-node to v2 #203

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 12, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@ivangabriele/tsconfig-node (source) 1.2.2 -> 2.0.0 age adoption passing confidence

Release Notes

ivangabriele/tsconfig (@​ivangabriele/tsconfig-node)

v2.0.0

Compare Source

⚠ BREAKING CHANGES
  • peer-deps: Require Next.js v14.
  • node: Set module & moduleResolution to Node16 instead of ESNext & Node.
  • next: Set moduleResolution to Bundler instead of Node.
  • Enable noImplicitReturns compiler option.
  • Remove ts-node config.
  • Enable exactOptionalPropertyTypes compiler option.
  • Enable verbatimModuleSyntax compiler option.
  • Migrate to ESM.
  • semantic-release: Require Typescript v5.
  • npm: Require Node.js v20+.
Features
  • enable exactOptionalPropertyTypes compiler option (86884af)
  • enable noImplicitReturns compiler option (d63182b)
  • enable verbatimModuleSyntax compiler option (69a63b5)
  • next: set moduleResolution to Bundler instead of Node (4c3b72b)
  • node: set module & moduleResolution to Node16 instead of ESNext & Node (b2265ad)
  • remove ts-node config (f1f4ba0)
Build System
Continuous Integration
  • semantic-release: setup (1f2d451)

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone Europe/Paris, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented Feb 21, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
Internal Error: ENOENT: no such file or directory, open '/home/ubuntu/.cache/node/corepack/lastKnownGood.json'
Error: ENOENT: no such file or directory, open '/home/ubuntu/.cache/node/corepack/lastKnownGood.json'

@renovate renovate bot force-pushed the renovate/ivangabriele-tsconfig-node-2.x branch from b8db250 to c8cd0bc Compare February 21, 2024 13:14
Copy link

coderabbitai bot commented Feb 21, 2024

Important

Auto Review Skipped

Bot user detected.

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

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-tests for this file.
  • 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 tests 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 from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants