fetch is not defined: using minimal client inside nuxt.config.js

Hey! It’s me again 😁

I’m using the minimal client inside nuxt.config.js in order to fetch all the routes at build time. I followed the approach you described here: https://github.com/nuxt-community/sanity-module/issues/3

// for minimal client
import { createClient } from '@nuxtjs/sanity'

const client = createClient({
  projectId: 'xxxxxxx',
  useCdn: false,
})

But when calling client.fetch, I get the error fetch is not defined. At first, I thought it was the property fetch on the client object that was undefined, but it’s actually the Fetch API that isn’t defined.

I know that, in this case, the runtime is Node, but I thought that the minimal client was isomorphic, because it works fine inside ayncData(). Also, I think that this used to work in previous versions of the module.

[danielroe]

@mornir Agreed - I think a very sensible approach. Using it in Nuxt config to generate routes shouldn’t add to your bundle size but why add another dependency if you don’t need to?

[mornir]

@danielroe Thanks for the quick reply! So I did it this way: https://github.com/mornir/movies-web/blob/dev/nuxt.config.js#L3

Now I no longer get the error fetch is undefined, but the results from client.fetch is now undefined (https://github.com/mornir/movies-web/blob/dev/nuxt.config.js#L72). Strange 🤔 Do you see anything wrong with my query?