Static example doesn't work with overriden output dir
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.2k
- Forks
- 1.8k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 6
Description
Hello,
I cloned static-files example, after that did (from the root):
ls -a
# Results in `. .. .vercel README.md`
mkdir test
mv .vercel test
ls -a
# Results in `. .. README.md`
ls -a test
# Results in `. .. .vercel`
Then I commited that to a repo and created a new project with given framework settings:
It resulted in 404 in deployments and single "static" file in Resources tab.
Without the inner dir hassle it works fine.
I guess it's something with Build Output API, but I couldn't find their repository to complain to.
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 with the build-output-api/static-files example and reproduce the deployment with .vercel moved into the test directory, comparing it with the working root-level layout. Trace how the overridden output directory is interpreted; done means the nested layout deploys without a 404 and does not appear as a single static resource.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100