`sapper export --entry` ignores file extensions

[WaltzingPenguin]

Describe the bug
sapper --export "/file.html" does not produce the expected result. I would expect it to navigate to the path "/file.html", triggering the code in file.html.svelte, and output this to "/file.html". Instead, it appears to navigate to "/file/", gets a 404, and tries to write out to "/file/index.html".

Behaviour on the dev server is as I would expect. "/file.html" returns the page I wrote, "/file/" returns a 404.

Logs

PS C:\www> npx sapper export --entry "/file.html" --build=false 
> Crawling http://localhost:3000/file/
   1.98 kB   (404) file/index.html
   1.87 kB   service-worker-index.html

> Finished in 885ms. Type npx serve __sapper__/export to run the app.

To Reproduce
Simply running npx sapper export --entry "/file.html" on any install does demonstrate the issue, since it starts the crawl at the wrong spot and outputs the wrong file.

Information about your Sapper Installation:

• Your operating system: Windows 10

• Your hosting environment: Local

• Sapper version: 0.27.8

• Svelte version: 3.9.1

Severity
An irritation for me. I was planning to use this to output 404.html, 500.html, etc for static hosting purposes. This makes it more difficult to output files not named index.html at the root level.

[khrome83]

The entry parameter takes a URL path. Try using “/file” instead. Export works by starting sapper in server mode and crawling the site. Hence why entry is a url instead of a file name.

…

--- Zane Milakovic

On Sep 3, 2019, 4:34 PM -0500, ADantes ***@***.***>, wrote: Describe the bug sapper --export "/file.html" does not produce the expected result. I would expect it to navigate to the path "/file.html", triggering the code in file.html.svelte, and output this to "/file.html". Instead, it appears to navigate to "/file/", gets a 404, and tries to write out to "/file/index.html". Behaviour on the dev server is as I would expect. "/file.html" returns the page I wrote, "/file/" returns a 404. Logs PS C:\www> npx sapper export --entry "/404.html" --build=false > Crawling http://localhost:3000/404/ 1.98 kB (404) 404/index.html 1.87 kB service-worker-index.html > Finished in 885ms. Type npx serve __sapper__/export to run the app. To Reproduce Simply running npx sapper export --entry "/file.html" on any install does demonstrate the issue, since it starts the crawl at the wrong spot and outputs the wrong file. Information about your Sapper Installation: • > Your operating system: Windows 10 • > Your hosting environment: Local • > Sapper version: 0.27.8 • > Svelte version: 3.9.1 Severity An irritation for me. I was planning to use this to output 404.html, 500.html, etc for static hosting purposes. This makes it more difficult to output files not named index.html at the root level. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[WaltzingPenguin]

For clarification:

When I type npx sapper export --entry "/file.html" I expect to see back:

Crawling http://localhost:3000/file.html

Instead, I see:

Crawling http://localhost:3000/file/

These are two unique urls, that each resolve to potentially different resources. Visiting the respective urls in the browser shows exactly what I would expect, there's just no way to convince export that I did indeed type what I meant.

[Conduitry]

Oh, that's interesting. Hm. @pngwn What do you think about this? When you implemented this, did you purposefully strip file extensions from the paths?

[pngwn]

Yeah, I did. I'll take a look at this.

[webspilka]

At my site I have redirect to folder with trail slash
domain.com/file.html -> domain.com/file.html/
I remove trail slash by add to .htaccess

DirectorySlash Off

# internally add the slash back
RewriteCond %{REQUEST_FILENAME} -d
RewriteCond %{REQUEST_URI} !/$
RewriteRule ^(.*)$ /$1/ [L]

Now I have working domain.com/file.html - without trail slash,
but links
domain.com/test-page.html
domain.com/test-page.html/index.html
keep working. I'm looking for a way to redirect these links to my domain.com/test-page.html

It would be great to export to a file
routes/test-page.html.svelte -> to file /test-page.html
then I would not have to use .htaccess