Replies: 2 comments 2 replies
-
Sorry, I resolved it myself again. import {GatsbyNode} from 'gatsby';
// cf. https://www.gatsbyjs.com/docs/how-to/custom-configuration/add-custom-webpack-config/
export const onCreateWebpackConfig: GatsbyNode['onCreateWebpackConfig'] = async ({ actions }) => {
actions.setWebpackConfig({
watchOptions: {
ignored: [`${__dirname}/src/gatsby-types.d.ts`]
},
plugins: [new ForkTsCheckerWebpackPlugin()]
});
}; |
Beta Was this translation helpful? Give feedback.
2 replies
-
I'm going to close this and start a new one in Ideas / Feature Request category. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm stuck in an infinite loop of Fast Refresh when I enabled type-checking in the way discussed in #37983 with GraphQL Typegen.
gatsby-types.d.ts
(This is due to the type-checking)gatsby-types.d.ts
is re-createdgatsby-types.d.ts
is changed, Fast Refresh runs and thengatsby-types.d.ts
is re-createdgatsby-types.d.ts
is changed, Fast Refresh runs and thengatsby-types.d.ts
is re-createdBeta Was this translation helpful? Give feedback.
All reactions