nuxt-community/composition-api

async functions require extra time with `nuxt generate`

Open

#44 opened on May 8, 2020

View on GitHub
 (10 comments) (0 reactions) (1 assignee)TypeScript (97 forks)auto 404
help wanted

Repository metrics

Stars
 (702 stars)
PR merge metrics
 (PR metrics pending)

Description

🐛 The bug When generated files are produced, async functions or serverPrefetches don't correctly populate the Nuxt context.

Note: I believe this is an issue with Nuxt rather than with nuxt-composition-api.

🛠️ To reproduce Steps to reproduce the behavior:

  1. Clone this repo.
  2. Remove interval: 2000 from test/fixture/nuxt.config.js
  3. Run yarn nuxt generate -c test/fixture/nuxt.config.js
  4. Inspect ./dist/ssr-ref/index.html to see not all ssrRefs injected in page

ℹ️ Workaround You can add time between pages being generated to allow for any async functions to resolve, if you are pre-generating any of your pages.

nuxt.config.js:

{
  generate: {
    // choose to suit your project
    interval: 2000,
  }
}

Contributor guide

Research direction
Investigate how Nuxt generate handles async functions in composition API setup, focusing on the generate hook timing and context population.
Tech stack
typescriptvuenodejs
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
NuxtVueasync/await
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60