`adapter-static` does not output to root of `dist` folder

[atjn]

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

When I try to run marko-run build, it will output the built files to dist/public. When I then upload the files to my file server, the front page of my website (example.com) will return a 404 error because there is nothing in the root folder. You must navigate to example.com/public to see the front page.

I think the behavior of the static adapter should be changed to always output files to the root folder. If you don't agree with that, I would request that you add an option to the configuration that allows me to put the files in the root folder.

[coderabbitai]

A summary of the changes CodeRabbit can apply:

• Add a new optional assetsDir option (default "public") to packages/adapters/static/src/index.ts, use it when extracting options and updating startPreview and buildEnd paths so assets can be emitted to dist/ (or any relative path like "."), and update packages/adapters/static/README.md with examples and usage.

• Remove packages/adapters/static/README.md and update packages/adapters/static/src/index.ts to add a new assetsDir option (default "public") with docs, introduce assetsDir variable, and replace hard-coded "public" paths with path.join(..., assetsDir) for static serving and build output.

• ✅ Create PR with these edits
• 📋 Get copyable edits

[DylanPiercey]

@atjn the reason this is the case is that for non static apps there must be both server and client assets. The client assets are added to the public folder. For consistency sake the static builds also output their assets to `dist/public.

[atjn]

Hell @DylanPiercey thank you for the answer. If you prefer to do it that way, that is up to you. I would prefer if it used the root of dist as the root of the page. I think this is a pretty common expectation for static file outputs, at least that is how Vite, Nuxt, Astro, Qwik City, and Sveltekit do it.

It would be helpful to me if you could add a setting to change that behavior, otherwise I would need to run a custom script afterwards to manually remove the folder structure. I would guess that I am not the only one for whom this setting would be useful.