Repository navigation
Replies: 3 comments
|
Converted to Q&A discussion as this doesn't meet our requirements for an issue. Might want to run this by vscode or nuxt folks |
|
exactly same issue, anybody got clue how to fix it? |
|
I can reproduce A workaround that keeps type checking (without import { defineNuxtConfig } from 'nuxt/config';
import graphql from '@rollup/plugin-graphql';
export default defineNuxtConfig({
vite: {
plugins: [graphql()],
},
nitro: {
hooks: {
'rollup:before': (_nitro, config) => {
config.plugins = [config.plugins, graphql()];
},
},
},
});Remove the original Verification on that pinned dependency set:
This was an isolated configuration/type-check and GraphQL bundle test on Node 24/Linux, not a full Nuxt application build or a reproduction of your macOS/Node 18 editor environment. Also keep the lockfile when comparing: installing this old Nuxt version with today's unconstrained transitive dependencies initially gave me a different Rollup 3/4 plugin-type incompatibility. That is separate from the |
Uh oh!
There was an error while loading. Please reload this page.
nuxt.config.ts
When added in this way, it works fine in operation.
However, on the VSCode editor, an error is displayed at the
graphql()point on the nitro side.Is this an error that only occurs with nuxt.config.ts?
How can I resolve this?
All reactions