Hi, I caught up finally. Not sure but is seems you're running it with ts-node so that's why? You need webpack with graphql-let/loader properly cofigured.
Hi, the application is a nextjs web app with Typescript. This is the webpack config section in the next.config.js:
webpack: (config, options) => { config.resolve.alias["components"] = path.join(__dirname, "components"); config.resolve.alias["lib"] = path.join(__dirname, "lib"); config.resolve.alias["public"] = path.join(__dirname, "public"); config.resolve.alias["server"] = path.join(__dirname, "server"); config.module.rules.push({ test: /\.graphql$/, exclude: /node_modules/, use: [options.defaultLoaders.babel, { loader: "graphql-let/loader" }], }); config.module.rules.push({ test: /\.graphqls$/, exclude: /node_modules/, use: ["graphql-tag/loader", "graphql-let/schema/loader"], }); return config; }
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi, I caught up finally. Not sure but is seems you're running it with ts-node so that's why? You need webpack with graphql-let/loader properly cofigured.
Hi, the application is a nextjs web app with Typescript. This is the webpack config section in the next.config.js: