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

chore(deps): update dependency vite-tsconfig-paths to v5 #349

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 22, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite-tsconfig-paths ~4.2.0 -> ~5.1.0 age adoption passing confidence

Release Notes

aleclarson/vite-tsconfig-paths (vite-tsconfig-paths)

v5.1.3

Compare Source

  • fix: Once an importer is matched, end directory traversal (b0d8ecb)
  • feat: Add vite-tsconfig-paths:resolve debug logs (7160d6e)
  • chore: Ensure debug logs can be enabled in vitest (0dc9a8b)

v5.1.2

Compare Source

  • fix Windows regression introduced in v5.1.1 (#​162)

v5.1.1

Compare Source

  • support ${configDir} syntax in include/exclude (#​156)

v5.1.0

Compare Source

  • Add skip option for adding additional directories to be skipped when searching for tsconfig.json files (#​146)
  • Fix path resolution on Windows when other Vite plugins neglect to normalize the importer path before calling this.resolve in their resolveId hooks (#​157)
  • Allow both tsconfig.json and jsconfig.json in the same directory (4124b09)

v5.0.1

Compare Source

v5.0.0

Compare Source

This package is now ESM only in order to align with Vite: https://vitejs.dev/guide/migration#deprecate-cjs-node-api

If your project is using CommonJS, you can rename your Vite config to use the .mjs or .mts extension (depending on whether you use TypeScript or not). If you're not using Vite v5.0.0+, you may want to pin your dependency to v4 of this plugin.

v4.3.2

Compare Source

v4.3.1

Compare Source

v4.3.0

Compare Source

v4.2.3

Compare Source

v4.2.2

Compare Source

v4.2.1

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Aug 22, 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: pnpm-lock.yaml
Scope: all 14 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
.                                        |  WARN  deprecated [email protected]
Progress: resolved 48, reused 0, downloaded 0, added 0
Progress: resolved 54, reused 0, downloaded 0, added 0
Progress: resolved 263, reused 0, downloaded 0, added 0
Progress: resolved 446, reused 0, downloaded 0, added 0
Progress: resolved 559, reused 0, downloaded 0, added 0
Progress: resolved 686, reused 0, downloaded 0, added 0
Progress: resolved 964, reused 0, downloaded 0, added 0
Progress: resolved 1067, reused 0, downloaded 0, added 0
Progress: resolved 1199, reused 0, downloaded 0, added 0
Progress: resolved 1304, reused 0, downloaded 0, added 0
Progress: resolved 1337, reused 0, downloaded 0, added 0
Progress: resolved 1538, reused 0, downloaded 0, added 0
Progress: resolved 1607, reused 0, downloaded 0, added 0
Progress: resolved 1716, reused 0, downloaded 0, added 0
Progress: resolved 1751, reused 0, downloaded 0, added 0
Progress: resolved 1888, reused 0, downloaded 0, added 0
Progress: resolved 2002, reused 0, downloaded 0, added 0
 WARN  28 deprecated subdependencies found: @babel/[email protected], @babel/[email protected], @babel/[email protected], @babel/[email protected], @babel/[email protected], @babel/[email protected], @humanwhocodes/[email protected], @humanwhocodes/[email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Progress: resolved 2002, reused 0, downloaded 0, added 0, done
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

apps/vite
└─┬ vite-tsconfig-paths 5.1.4
  └─┬ tsconfck 3.1.4
    └── ✕ unmet peer typescript@^5.0.0: found 4.9.3

hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.


@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch 7 times, most recently from eda0468 to 88617cc Compare September 2, 2024 16:37
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch from 88617cc to 59b0fb0 Compare September 7, 2024 01:32
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch 2 times, most recently from 30011e7 to 4800b88 Compare September 24, 2024 10:37
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch 4 times, most recently from f37863b to 799dbb7 Compare October 7, 2024 12:04
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch 4 times, most recently from 88e2189 to 276c5b1 Compare October 16, 2024 18:43
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch from 276c5b1 to 3e3e446 Compare October 17, 2024 16:29
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch 3 times, most recently from 5ac57d9 to 47d4bac Compare November 4, 2024 23:02
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch 3 times, most recently from 063f03e to d5191c6 Compare November 15, 2024 01:26
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch 3 times, most recently from cfe0076 to 6ddb552 Compare November 23, 2024 13:01
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch from 6ddb552 to a5b2d60 Compare November 27, 2024 14:09
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch 2 times, most recently from 8ee748f to 00fa5eb Compare November 29, 2024 15:45
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch 2 times, most recently from b07050d to ab3cf12 Compare December 14, 2024 18:51
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-5.x branch from ab3cf12 to 664e210 Compare December 17, 2024 17:18
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.

0 participants