-
Notifications
You must be signed in to change notification settings - Fork 26.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamic catch-all routes not supported in Google App Engine #10556
Comments
I'm also having this problem. The problem only occurs on the App Engine Standard environment. |
Now, this is extremely annoying :( |
I'm running into this problem right now as well. Any known workarounds would be greatly appreciated |
Same problem here! It's blocking our project at the moment. |
Same here. One workaround is to duplicate code for every sub-path (I did for 3 levels) |
Do you have an example of what you did to achieve this? |
I think he created the same workaround I did. Import and directly export the associated route component in every subpath, which in essence will duplicate that component for every subpath. |
That's correct - I didn't see this before now. |
Anyone has a workaround without duplicating code for every path ? |
Not that I'm aware of. Hopefully this is fixed soon! |
This is blocking our production release :( |
+1 |
I made the following workaround and it seems to work fine.
Invoke |
How much increased startup time did you see? I have an application where every MS counts. |
Did anyone file a bug report with GAE to allow this valid file name? |
Yes. I reported it through GAE feedback about the same time. I'm not sure what channel to report that specific thing to. |
How shall I deploy the next.js app on compute engine, any idea. |
@Timer Google has fixed this on their end now. Closing issue. |
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Issue with filename-name causing deploy error in Google App Engine
Describe the bug
I've had a nextJS app running in the Google App Engine enviroment for a while. Works splendid and fast - however, I added a dynamic route and now I am unable to deploy due to the filename being unsupported (due to the 3 dots).
Error from the Gcloud CLI:
ERROR: (gcloud.app.deploy) INVALID_ARGUMENT: Filename cannot contain '.', '..', '\r', start with '-', '_ah/', or '\n': pages/[...slug]/index.js
.One fix could be using underscore or similar instead, like "[___slug]"
To Reproduce
Deploy the app to Google App Engine using any boilerplate configuration for app.yaml with a dynamic catch all route. Use below example and add a catch-all page.
https://github.com/superbmeteor/nextjs-gae-demo
Expected behavior
Should deploy successfully.
The text was updated successfully, but these errors were encountered: