Skip to content

chore: make swc_ecma_lint optional for swc crate #10767

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

Merged
merged 2 commits into from
Jul 3, 2025

Conversation

hardfist
Copy link
Collaborator

@hardfist hardfist commented Jul 3, 2025

Description:
swc_ecma_lint is not necessary for parser & transform, so make it optional for Rust API users

BREAKING CHANGE:

Related issue (if exists):

@hardfist hardfist requested a review from a team as a code owner July 3, 2025 07:58
Copy link

changeset-bot bot commented Jul 3, 2025

🦋 Changeset detected

Latest commit: 4c5a9ad

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@hardfist hardfist changed the title chore: make swc_ecma_lint optional chore: make swc_ecma_lint optional for swc crate Jul 3, 2025
Copy link
Member

@kdy1 kdy1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kdy1 kdy1 added this to the Planned milestone Jul 3, 2025
@kdy1 kdy1 requested a review from a team as a code owner July 3, 2025 13:04
@kdy1 kdy1 merged commit f80415b into swc-project:main Jul 3, 2025
18 checks passed
Copy link

codspeed-hq bot commented Jul 3, 2025

CodSpeed Performance Report

Merging #10767 will not alter performance

Comparing hardfist:yj/make-lint-optional (4c5a9ad) with main (ce5138d)

Summary

✅ 141 untouched benchmarks

@kdy1 kdy1 modified the milestones: Planned, v1.12.10 Jul 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants