Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Dynamic catch-all routes not supported in Google App Engine
See original GitHub issueIssue 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.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:16
- Comments:19 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Same problem here! It’s blocking our project at the moment.
I’m running into this problem right now as well. Any known workarounds would be greatly appreciated