[DT-400-npm]: Bump vite-tsconfig-paths from 4.3.2 to 6.0.3

[dependabot]

Bumps vite-tsconfig-paths from 4.3.2 to 6.0.3.

Release notes

Sourced from vite-tsconfig-paths's releases.

v6.0.0

Highlights

• On-demand tsconfig discovery via projectDiscovery: "lazy", while eager discovery remains the default.
• tsconfig/jsconfig files are watched and reloaded automatically in both modes, including during vite build --watch.
• New logFile option for per-import resolution traces (pass true for vite-tsconfig-paths.log or provide a path).
• Support for root /* aliases and other absolute-style imports.
• Support for .astro files when allowJs/loose is enabled.

Fixes

• More reliable tsconfig watching and resolver refreshes: handles lazy discovery edge cases, recreates resolvers after file changes, tolerates missing directories, and copes better with virtual importers.
• Windows path handling now normalizes drive-letter casing to avoid missed matches (#183).

Upgrade notes

• Install the stable release: pnpm add -D vite-tsconfig-paths.
• Opt into lazy discovery or logging when needed:

import tsconfigPaths from 'vite-tsconfig-paths'
export default {
plugins: [
tsconfigPaths({
projectDiscovery: 'lazy',
logFile: true,
}),
],
}

• Rooted path patterns such as "/*": ["src/*"] now resolve the same way tsserver does.

v6.0.0-beta.4

• fix(windows): ensure drive letter is uppercase (#183)
• feat: add .astro to JS-like extension regex (fbbc8edb86606c612565a6672c8e0ae93f0001a0)

v6.0.0-beta.3

• Added support for /* path aliases. (#101)

v6.0.0-beta.2

• Added a new logFile option.
  Pass logFile: true and the plugin will create a vite-tsconfig-paths.log file in your working directory.

  Using DEBUG=vite-tsconfig-paths in the past has worked pretty well, but it isn't always the most readable. In v6 and above, this plugin will still have debug logs using this approach, but module resolution will only be logged through the new logFile option. The log file will be comprehensive (as in, every import that vite-tsconfig-paths receives will be logged). If an import goes unhandled by this plugin, the reason will be logged. If an import is resolved, the resolved path and the tsconfig path are both logged. In fact, every possible code path (in the context of module resolution) is logged to the log file.

• Universal support for tsconfig reloading.
  Whether you're using projectDiscovery: "lazy" or eager loading, this plugin should now be able to watch and reload tsconfig files when you make changes to them. This feature hasn't been rigorously tested yet. Please report issues you come across.

... (truncated)

Commits

• 6b0e61c chore: release v6.0.3
• 3d97cb4 fix: ensure project references don’t get lost
• 6119433 chore(test): add control over -p value of tsc
• 04e4602 chore(test): add case for common “project reference” pattern (#198)
• 0f27ad2 chore(docs): mention vite-postgres
• 4228a54 chore: release v6.0.2
• cf7147c fix: ensure all paths are normalized for Windows compatibility (#196)
• 3d029d9 chore(test): add logs for vite module resolution
• 2da87a8 chore(test): run tests sequentially in CI
• b9a5a81 chore(test): enable debug logs in test suite
• Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
vite-tsconfig-paths	[>= 5.a, < 6]

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cypress]

jade-data-repo-ui    Run #4651

Run Properties:   Passed #4651  •  f47d2e3fd3 ℹ️: Merge 7d31309fc5753b1ea41d4cc5c43f07cd9babe7df into fbb05298e41bc6d888a5c29a9d78...

Project	jade-data-repo-ui
Branch Review	dependabot/npm_and_yarn/vite-tsconfig-paths-6.0.3
Run status	Passed #4651
Run duration	00m 41s
Commit	f47d2e3fd3 ℹ️: Merge 7d31309fc5753b1ea41d4cc5c43f07cd9babe7df into fbb05298e41bc6d888a5c29a9d78...
Committer	dependabot[bot]
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	0
Skipped	0
Passing	4
View all changes introduced in this branch ↗︎

[davidangb]

Hm, looks like we previously ignored vite-tsconfig-paths 5.x, in
#1686. In that PR, engineers landed on staying on 4.x of this dependency. Should we also ignore vite-tsconfig-paths 6.x?

[rjohanek]

Hm, looks like we previously ignored vite-tsconfig-paths 5.x, in #1686. In that PR, engineers landed on staying on 4.x of this dependency. Should we also ignore vite-tsconfig-paths 6.x?

Do you have context surrounding that decision? Why were we ignoring updates?

[snf2ye]

It looks like we previously ignored this because we were on an old version of vite. I wonder if we can upgrade this to match vite v6.

[davidangb]

Do you have context surrounding that decision? Why were we ignoring updates?

@rjohanek I do not have any context; I was just curious about why this PR had a big version jump and so I looked through history and found that other PR

[dependabot]

Superseded by #1856.