Repository navigation
chore(build): remove redundant vite-tsconfig-paths plugin - #250
Merged
Merged
Conversation
Vite 8 reports that tsconfig path resolution is built in and the plugin is no longer needed. Both vite.config.ts and vitest.config.ts already define the same mappings as explicit resolve.alias entries (@, @shared), which cover every path in tsconfig.json (@/*, @shared/*), so the plugin added nothing. Remove the plugin from both configs and the dependency, including its exclusive transitive packages (tsconfck, globrex). No switch to resolve.tsconfigPaths and no alias changes. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes the
vite-tsconfig-pathsplugin. Vite 8 prints on every dev server and test start:The plugin is redundant here, so it is removed rather than migrated to
resolve.tsconfigPaths: true:vite.config.tsandvitest.config.tsalready define the same mappings as explicitresolve.aliasentries (@,@shared).tsconfig.jsondeclares only@/*and@shared/*, both covered by those aliases.Changes
vite.config.ts,vitest.config.ts: drop the import andtsconfigPaths().package.json,package-lock.json: drop the dependency and its exclusive transitive packages (tsconfck,globrex).Not changed: no
resolve.tsconfigPaths, no alias refactor.tsconfig.jsonpathsstay, they still servetscandtsx.Verification
npm ci,npm run check,npm run lint,npm run check:docs,npm run build(total bundle size unchanged: 3,995,542 bytes),npm run test:unit(309 files / 3061 tests passed).npm run dev:client): started without a resolve error; the page and every module reachable from the entry were requested (152 modules: 113 under/src, 10 fromshared, 23 pre-bundled deps; 0 non-200 responses). In the repo, 76 client files import@/…and 39 import@shared/…./apirequests aborted): the app root rendered, no Vite error overlay, no resolve/pre-transform errors../run-tests.sh(static analysis, knip, unit, toolchain integration, Docker, Playwright E2E, production build, security audit, Sonar gate with 0 violations).Based on current
main; independent of #249.🤖 Generated with Claude Code