feat(gatsby): Includes ts/tsx files to eslint rules

[ashr81]

Description

Includes ts/tsx files extensions to check for the eslint rules.

Fixes #15114

[ashr81]

@wardpeet can you please rerun the tests. They failed because of GitHub downtime.

[wardpeet]

Sweet thank you for taking this on! Looks great!

No comments 👏

[gatsbot]

Holy buckets, @ashr81 — we just merged your PR to Gatsby! 💪💜

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. We’ve got Gatsby t-shirts, stickers, hats, scrunchies, and much more. (You can also unlock even more free swag with 5 contributions — wink wink nudge nudge.) See gatsby.dev/swag for details.
2. We just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. Accept the invite by visiting https://github.com/orgs/gatsbyjs/invitation. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again!

[me4502]

This appears to have broken builds of Gatsby sites using Typescript, as they're now expecting TypeScript files to just use JavaScript syntax?

Edit: Only in develop mode

[wardpeet]

rolled back in [email protected]

[ashr81]

@wardpeet what shall I do to fix this issue?

[LekoArts]

I don't think the initial issue was valuable anyways. typescript-eslint is outdated (you now use eslint) and a typical Gatsby project is still JS, not TypeScript. People who want to use TypeScript can probably setup their own eslint setup.

[ashr81]

@LekoArts Ok, Makes sense.

[ThewBear]

@ashr81 You have to also move eslint-config-react-app to ^4.0.0 for typescript support otherwise it will fail all typescript files.

[wardpeet]

we've reverted the change for now as it seems to give some troubles in monorepos