`--nextless` breaks if `src/pages` structure is used

Open
#58 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
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
nextjs, typescript
Domain
build-system

Research direction

Start by reproducing the issue with a project using a src/pages structure and the --nextless option. Inspect the generated .nsm/generated_routes.ts manifest and compare its paths with the project's page structure; done means the manifest contains valid paths for this layout.

Written by the indexing model from the issue text.

Description

If a project uses a src/pages structure (instead of /pages), --nextless will generate a .nsm/generated_routes.ts manifest with invalid paths.

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.