[v2] Typescript plugin not working

[jaredpalmer]

Description

I tried to use the typescript plugin with v2 to no avail. I get the following error message.

ERROR in ./src/pages/index.tsx
Module parse failed: Unexpected token (3:7)
You may need an appropriate loader to handle this file type.
| import * as React from 'react';
|
| export interface IndexProps {}
|
| export interface IndexState {}
 @ ./.cache/sync-requires.js 11:51-124
 @ ./.cache/root.js
 @ ./.cache/app.js
 @ multi ./node_modules/react-hot-loader/patch.js (webpack)-hot-middleware/client.js?path=http://localhost:8000/__webpack_hmr&reload=true&overlay=false ./.cache/app
ℹ ｢wdm｣: Failed to compile.

Environment

• Gatsby version (npm list gatsby): 2.0.0-alpha.40
• gatsby-cli version (gatsby --version):
• Node.js version: 8.9.x
• Operating System: macOS Sierra

File contents (if changed)

gatsby-config.js:

module.exports = {
  plugins: [`gatsby-plugin-typescript`, `gatsby-plugin-react-helmet`],
};

package.json: N/A
gatsby-node.js: N/A
gatsby-browser.js: N/A
gatsby-ssr.js: N/A

[KyleAMathews]

Hmm not sure — you can check out the source here to see if something looks awry https://github.com/gatsbyjs/gatsby/blob/v2/packages/gatsby-plugin-typescript/src/gatsby-node.js#L14

[jaredpalmer]

Why are you adding the js loaders here?

https://github.com/gatsbyjs/gatsby/blob/v2/packages/gatsby-plugin-typescript/src/gatsby-node.js#L39

[KyleAMathews]

Not sure — @jquense wrote this so I'll you off to him ;-)

[jaredpalmer]

hmmm onCreateWebpack config is not even getting fired... i just threw an error in there and nothin happened.

[KyleAMathews]

Hmm are any of the functions being called?

[jaredpalmer]

confirmed that resolvableExtensions is def getting called

[jaredpalmer]

confirmed that preprocessSource is too.

[KyleAMathews]

Odd — this is where the API is called — perhaps there's a subtle typo or something?

gatsby/packages/gatsby/src/utils/webpack.config.js

Line 411 in 81ebfc7

await apiRunnerNode(`onCreateWebpackConfig`, {

Is there any console errors?

[jaredpalmer]

oh well v2 of typescript plugin is using actions.setWebpackConfig it's not merging and returning.

[jaredpalmer]

actions is not being passed to the code you just linked to.

[mquandalle]

So #5522 fixes this issue?

[jaredpalmer]

#5522 and the TypeScript plugin needs a newer version of ts-loader that's compat with Webpack 4

[jquense]

Why are you adding the js loaders here?

#3369

I've never felt like that was a good choice tho...especially now that babel has a TS parser

[mquandalle]

Indeed NextJS 6 uses babel parser for Typescript which integrates better with the build toolchain (you still get the TS experience in the editor)