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 #268

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 15, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite-tsconfig-paths 3.5.0 -> 5.1.2 age adoption passing confidence

Release Notes

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

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

v4.2.0

Compare Source

  • 7a97869 If a tsconfig file is malformed and cannot be parsed (e.g. its extends property points to a non-existent file), an error is now logged instead of crashing the process. You can disable parsing error logs by setting ignoreConfigErrors: true in the plugin options.

v4.1.0

Compare Source

  • 9766de8 If the projects option is used, any missing tsconfig files will be silently ignored (other than a debug log, enabled with DEBUG="vite-tsconfig-paths" environment variable).

v4.0.9

Compare Source

v4.0.8

Compare Source

v4.0.7

Compare Source

v4.0.6

Compare Source

v4.0.5

Compare Source

v4.0.4

Compare Source

v4.0.3

Compare Source

v4.0.2

Compare Source

v4.0.1

Compare Source

v4.0.0

Compare Source

  • Stop using the tsconfig-paths package
    It is better to let Vite handle all of the resolving, so that this plugin can be only responsible for the path mapping.

    At the same time, I am also adding the tsconfck package, which handles the loading of tsconfig.json files for us. This package is also used in Vite core (we should have Vite expose it in the future, to avoid the duplication).

    The tsconfig-paths package was previously responsible for config loading and much of the path resolving logic, but now we can ditch it! I'm also ditching the recrawl-sync package, which was used for crawling the filesystem in search of tsconfig.json files.

  • Remove the extensions option
    Since the file resolution is delegated to Vite core, this option is no longer necessary.

  • Add the parseNative option
    The tsconfck package has a parseNative function that's able to delegate config loading to the TypeScript compiler. If you encounter a bug in tsconfig.json file loading, you can try passing parseNative: true to see if that helps. But you should avoid enabling it otherwise, since it has a noticeable performance cost (up to 600ms roughly speaking).

v3.6.0

Compare Source

v3.5.2

Compare Source

v3.5.1

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.

Copy link

vercel bot commented Aug 15, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
devbox ❌ Failed (Inspect) Nov 10, 2024 6:25pm

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

Successfully merging this pull request may close these issues.

0 participants