Import nuxt files on runtime
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 41m
- Merged PRs (30d)
- 2
Description
At the moment, if one script get loaded, e. g. a schema or fixture which imports virtual files like import {useRuntimeConfig} from '#imports'; the command will fail because the cli does not know anything about nuxt.
This problem cause a bad dx, because scripts, called from this cli need to be handled way to carefuly
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the CLI path that loads scripts such as schemas or fixtures, then inspect how imports like #imports are handled when Nuxt is not known to the CLI. Done means a loaded script using Nuxt virtual files can run successfully without special handling by the caller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- cli, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100