Serve public files

Open
#64 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
next.js, typescript
Domain
backend, web-dev

Research direction

The issue names Next.js's public/* path and the next dev entry point, but no repository file or test. Start by tracing the embedded Next.js server's handling of requests to public/*, then verify that a file placed there is served at the root instead of returning 404.

Written by the indexing model from the issue text.

Description

Next.js (next dev, etc.) will serves public files from public/* at the root. With nsm those files return 404 errors.

Dominant language
TypeScript
Stars
5
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seamapi/nextjs-server-modules

All issues in seamapi/nextjs-server-modules

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.