Skip to content

fix: use type-only imports whenever possible #460

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Nov 6, 2025
Merged

fix: use type-only imports whenever possible #460

merged 1 commit into from
Nov 6, 2025

Conversation

@lppedd
Copy link
Contributor

@lppedd lppedd commented Nov 6, 2025

This PR introduces two fundamental ESLint rules:

@typescript-eslint/no-import-type-side-effects
@typescript-eslint/consistent-type-imports

Which help avoiding situations where tsc keeps empty imports.

Fixes #459

@danielpza danielpza self-requested a review November 6, 2025 11:41
@danielpza danielpza merged commit 5f4b3bd into LeDDGroup:master Nov 6, 2025
7 checks passed
@lppedd lppedd deleted the fix/types branch November 6, 2025 11:59
@danielpza
Copy link
Member

danielpza commented Nov 6, 2025

Thank you
Published in typescript-transform-paths@4.0.0-beta.2

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

Reviewers

@danielpza danielpza danielpza approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Nx transformer plugin cannot be loaded on v4 beta

2 participants

@lppedd @danielpza