After migrating to vite, routes with a "." do not work anymore

[nhnb]

After migrating to vite, routes with a "." do not work anymore

[JeanMeche]

Hi,
I looks like the same as #27657

[alan-agius4]

Why do you include file extensions in your SPA routes? Including file extensions in routes is often due to legacy systems or a desire for clarity. However, this practice isn't ideal for SPAs as modern best practices favor clean, extensionless URLs. They enhance user experience, aid SEO, and ensure consistency across routes.

[nhnb]

Exactly those two reasons:

1. Keeping existing URLs working

2. Communicating to users that this is a "stable" URL, that can safely be shared. Our users also work with Webflow based systems in which the URL consists of a flow key and will not work after logout / for other users. (We do have a "share"-button, but people like to copy URLs from the address-bar anyway.)

So yeah, we could rewrite URLs on the webserver to deal with 1). And we could try to educate users, that the URLs in our system are stable for 2).

I did not test this case: Would an URL like https://example.com/angularapp/share/My+Thesis+1.+Draft cause the same issue?

I realize that the issue only affects developers, so it's not a big deal.

[alan-agius4]

I did not test this case: Would an URL like https://example.com/angularapp/share/My+Thesis+1.+Draft cause the same issue?

No, that would work. The issue with heroes-list.html arises because the route contains a valid file extension, and hence the code path for static files is being triggered.