Skip to content
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

chore: Use tsx directly instead of via esno #213

Merged
merged 1 commit into from
Jul 13, 2024

Conversation

Wxh16144
Copy link
Contributor

@Wxh16144 Wxh16144 commented Jul 12, 2024

Description

This fixes compatibility problems with later version of node v18.

See here for more details: privatenumber/tsx#421

Linked Issues

image ### Additional context

This fixes compatibility problems with later version of node v18. See here for more details: privatenumber/tsx#421
@Wxh16144
Copy link
Contributor Author

Another solution is to upgrade esno to 4.7.0, but esno has already become an alias for tsx, I think it can be directly replaced.

@antfu antfu merged commit c929426 into antfu-collective:main Jul 13, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants