Camel Casing Route Handler Folder Names #69877
Comments
github-actions
bot
added
the
invalid link
|
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully. Why was this issue closed?To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router. The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.
What should I do?Depending on the reason the issue was closed, you can do the following:
In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue. My repository is private and cannot make it publicIn most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:
I did not open this issue, but it is relevant to me, what can I do to help?Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue. I think my reproduction is good enough, why aren't you looking into it quickly?We look into every Next.js issue and constantly monitor open issues for new comments. However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority. Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it. Useful Resources |
Link to the code that reproduces this issue
https://music.apple.com/us/album/punk-star-ep/1764721837
To Reproduce
I am using
14.2.8and node20.11.0. I had to change my route handler folders to camel case before they worked in our production environment. They worked in dev as snake case but wouldn't work in production until I converted them to camel case.Current vs. Expected behavior
I am using
14.2.8and node20.11.0. I had to change my route handler folders to camel case before they worked in our production environment. They worked in dev as snake case but wouldn't work in production until I converted them to camel case.Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:59:33 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T8112 Available memory (MB): 24576 Available CPU cores: 8 Binaries: Node: 20.11.0 npm: 9.5.0 Yarn: 4.2.2 pnpm: N/A Relevant Packages: next: 14.2.8 // Latest available version is detected (14.2.8). eslint-config-next: 14.2.3 react: 18.3.1 react-dom: 18.3.1 typescript: 5.5.4 Next.js Config: output: standaloneWhich area(s) are affected? (Select all that apply)
Pages Router
Which stage(s) are affected? (Select all that apply)
next build (local), Other (Deployed)
Additional context
I am using
14.2.8and node20.11.0. I had to change my route handler folders to camel case before they worked in our production environment. They worked in dev as snake case but wouldn't work in production until I converted them to camel case.The text was updated successfully, but these errors were encountered: