feat: universal TypeScript import alias support and internal path alias refactoring #27
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
This PR removes the Next.js dependency for import alias configuration and refactors all internal imports in the Unrag package to use TypeScript path aliases.
Changes
Part 1: Universal Import Alias Support
Previously,
unrag initonly patchedtsconfig.jsonwhen Next.js was detected. Since Unrag is TypeScript-only, import aliases should work for any TypeScript project.Modified files:
packages/unrag/cli/commands/init.tspatchTsconfigPaths()for TypeScript projectsImpact:
Part 2: Internal Import Path Aliases
Refactored all internal imports to use clean path aliases instead of relative paths.
Created:
packages/unrag/tsconfig.jsonwith path mappings:@cli/*→./cli/*@registry/*→./registry/*@test/*→./test/*Updated ~80 files with ~180 import changes: