gatsby-source-graphql: Add babel typescript plugin and specify ts extension in build

[copperwall]

Description

This adds the .ts extension to the npm run build command so that babel doesn't only transform .js files in the src directory.

This also adds the @babel/plugin-transform-typescript babel plugin in the .babelrc so that .ts files are parsed correctly by babel.

I ran npm publish --dry-run to make sure the out files from the batching/*.ts files ended up in the package.

npm publish --dry-run

> gatsby-source-graphql@2.3.1 prepare .
> cross-env NODE_ENV=production npm run build


> gatsby-source-graphql@2.3.1 build /Users/zolokar/projects/gatsby/packages/gatsby-source-graphql
> babel src --out-dir . --ignore **/__tests__ --extensions ".ts,.js"

Successfully compiled 11 files with Babel.
npm notice 
npm notice 📦  gatsby-source-graphql@2.3.1
npm notice === Tarball Contents === 
npm notice 178B   .babelrc                   
npm notice 2.7kB  batching/dataloader-link.js
npm notice 2.6kB  gatsby-node.js             
npm notice 13B    index.js                   
npm notice 10.7kB batching/merge-queries.js  
npm notice 1.0kB  transforms.js              
npm notice 1.4kB  package.json               
npm notice 16.1kB CHANGELOG.md               
npm notice 9.4kB  README.md                  
npm notice === Tarball Details === 
npm notice name:          gatsby-source-graphql                   
npm notice version:       2.3.1                                   
npm notice package size:  10.7 kB                                 
npm notice unpacked size: 44.1 kB                                 
npm notice shasum:        65d77890da6496a98a09a0300ee559afd550364c
npm notice integrity:     sha512-x3Ub+ztY+rGSt[...]i7RdX+lF5FuyA==
npm notice total files:   9                                       
npm notice 
+ gatsby-source-graphql@2.3.1

Documentation

This shouldn't require a docs update.

Related Issues

Fixes #22785

[copperwall]

Sorry for the force-push, it looked like the integration_tests_cache_resilience ran into an issue and I wanted to rerun the build so I amended the last commit to cause a new push event.

[vladar]

Thank you for the PR! 💜

It would have fixed the underlying problem with TS build. But the issue is that we were using Typescript prematurely in gatsby-source-graphql.

For now, Gatsby plugins should not be using Typescript. When we are ready for Typescript in plugins we will come up with a common configuration for all Gatsby plugins.

So thank you so much for a quick fix but we will have to choose a different approach and just convert TS files to vanilla JS for now. See #22848 for a follow-up PR.

[copperwall]

No worries, thanks for letting me know!

Haha, I was trying to see if there was a more global setup in the gatsby repo for typescript builds, but I ended up just patching some thing together from another subpackage or two that was using TypeScript somehow.

Getting a more common configuration sounds good to me.