You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered a scenario in which assets generated by SvelteKit can’t be imported by the app due to the + (plus) sign being in the generated paths (after the routing update).
I have a setup in which a few pages of my Laravel app are generated by adapter-static. In production, assets would be served by Nginx, but the development environment relies on the built-in PHP server. After upgrading SvelteKit, I started getting weird redirects for all assets whose paths contained the + (plus) sign, e.g. +page-3508b0bd.css. It turns out that the PHP server treats the + (plus) character as a space (source)
I know it’s technically fine to use an unescaped + sign in a path, but it seems there might be edge cases where this causes problems.
Reproduction
Serve a statically-generated SvelteKit app (post-routing update) using the built-in PHP server.
Describe the bug
I have encountered a scenario in which assets generated by SvelteKit can’t be imported by the app due to the
+
(plus) sign being in the generated paths (after the routing update).I have a setup in which a few pages of my Laravel app are generated by
adapter-static
. In production, assets would be served by Nginx, but the development environment relies on the built-in PHP server. After upgrading SvelteKit, I started getting weird redirects for all assets whose paths contained the+
(plus) sign, e.g.+page-3508b0bd.css
. It turns out that the PHP server treats the+
(plus) character as a space (source)I know it’s technically fine to use an unescaped
+
sign in a path, but it seems there might be edge cases where this causes problems.Reproduction
Serve a statically-generated SvelteKit app (post-routing update) using the built-in PHP server.
Logs
No response
System Info
Severity
blocking an upgrade
Additional Information
No response
The text was updated successfully, but these errors were encountered: