-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(website): remove swc: true to fix builds #7167
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(website): remove swc: true to fix builds #7167
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I'm quite baffled by this as well. I'll take a look later. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh, the number of weirdities SWC has makes this really hard to debug. Do you think it's better to try adding an .swcrc
file? Or we can just get rid of SWC like this—it's only one config file, no big deal.
I have other PR for this problem #7182 - let's see if the build succeeds with that change :) |
Oop, I did this in |
PR Checklist
Overview
Stops using
swc: true
in ts-node so that the website will build again.