docs: clarify path matching behavior for route methods vs app.use() (#1941)#2045
Closed
kushal4345 wants to merge 2 commits intoexpressjs:gh-pagesfrom
Closed
docs: clarify path matching behavior for route methods vs app.use() (#1941)#2045kushal4345 wants to merge 2 commits intoexpressjs:gh-pagesfrom
kushal4345 wants to merge 2 commits intoexpressjs:gh-pagesfrom
Conversation
✅ Deploy Preview for expressjscom-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
🚦 Lighthouse Results (Mobile & Desktop)
|
Contributor
Author
|
I wanted to kindly follow up on my PR submitted about two weeks ago that updates the documentation to clarify the difference between app.use() prefix-based path matching and route methods’ exact path matching (addresses issue #1941). Please let me know if any further changes or adjustments are needed from my side. I’d be happy to make updates to help get it merged. |
ShubhamOulkar
requested changes
Sep 7, 2025
Member
ShubhamOulkar
left a comment
ShubhamOulkar
left a comment
There was a problem hiding this comment.
Similar examples are already present on following page
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR updates the documentation to address #1941 issue
Adds a note explaining that:
app.use() uses prefix-based path matching (e.g., /api will match /api/users).
HTTP method handlers (app.get(), app.post(), etc.) use exact path matching (e.g., app.get('/api') will only match /api).
Provides a clear code example to highlight the difference.
Ensures users are not confused when switching between app.use() and route methods.
This improves the clarity of the path examples section in the docs.