Fix routing for /new to prevent 404 errors #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request fixes a bug where users would see a 404 error page when navigating directly to the
/new
URL in their browser. The issue was caused by the"homepage"
property inpackage.json
, which has now been removed to allow the development server to correctly handle client-side routing.An additional end-to-end test has been added to
e2e/routing.spec.ts
to verify that a direct navigation to/new
successfully loads the welcome page, preventing future regressions.PR created automatically by Jules for task 447809867750893413