useFetch returns data.result === null on RC.6 in production mode.

Environment

Nuxt CLI v3.0.0-rc.6
RootDir: /Users/.../Documents/development/professional/MY_PROJECT
Nuxt project info:

------------------------------
- Operating System: `Darwin`
- Node Version:     `v18.6.0`
- Nuxt Version:     `3.0.0-rc.5`
- Package Manager:  `npm@8.13.2`
- Builder:          `vite`
- User Config:      `modules`, `head`, `css`, `vite`, `srcDir`, `progress`
- Runtime Modules:  `nuxt-progress@0.1.4`
- Build Modules:    `-`
------------------------------

Reproduction

I’m sorry, but I can’t reproduce the bug except on my project. However, I know the bug is due to the v3.0.0-rc.6 because I tried an old commit, with the v3.0.0-rc.4 so it was working. And just with upgrading to the rc.6, the bug appears. Using the code below, outside of my project, it’s working. But it was working on rc.4, so I don’t understand 😕

Describe the bug

useFetch returns data.value null on client (at the first fetch), but it seems to have a value on server. When I fetch again (with a “load more” button) I get my results.

<script lang="ts" setup>
import { useFetch } from '#app';

async function fetchArticles (): Promise<void> {
  articles.isLoading = true;
  const { data } = await useFetch<{ posts: GhostPage[] } & BrowseResults>('GHOST CONTENT API', {
    params: {
      key: 'API',
      include: ['authors', 'tags'].join(','),
      page: articles.currentPage
    },
    pick: ['posts', 'meta']
  });
  if (data.value.meta.pagination.pages === articles.currentPage)
    articles.hasMore = false;
  articles.data.push(...data.value.posts);
  articles.filteredData = filterArticles(articles.data);
  articles.isLoading = false;
}
</script>

Additional context

No response

Logs

No response

[danielroe]

I’m closing as RC8 is now out. Let me know if it wasn’t resolved and I’ll reopen!

[wzy1935]

@pi0 @danielroe Edge channel works for me, thanks! Looking forward to the final release👍