Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`adapter-static` add option to output subpages in subfolders

Open
  • Is something wrong?
#173 5 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
build-system, web-dev

Research direction

Start by reproducing the issue with the shown src/routes structure and marko-run build command. Inspect the adapter-static output handling and existing adapter options; done means a configurable build produces foo/index.html while preserving the root index.html and supports both /foo and /foo/.

Written by the indexing model from the issue text.

Description

I am using the default marko-run project with the adapter-static adapter..

When I create a route structure like this:

src/routes
├── foo
│   └── +page.marko
└── +page.marko

... and I run marko-run build, I get this output:

dist/public
├── foo.html
└── index.html

If I then copy these files to my file server and try to connect to my website, I cannot connect to the subpage. Connecting to example.com/foo or example.com/foo/ both return 404 errors. I must explicitly connect to example.com/foo.html to see the page.

I would prefer the output structure to look like this:

dist/public
├── foo
│   └── index.html
└── index.html

That would allow the server to correctly locate foo/index.html when connecting to either of example.com/foo or example.com/foo/. As far as I can tell, there is no option to enable this behavior. Is that something you could add?

Dominant language
TypeScript
Stars
175
Forks
16
Avg merge
3d 12h
Merged PRs (30d)
6

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 marko-js/run

All issues in marko-js/run

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.