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
error: "Serverless-offline: route not found." #911
Comments
My project also stopped working. Trying to hit any route now gives me this error:
|
Wait a minute, I have seen this before... ng-toolkit package right there! So this is related to #905 and hence, to my comment. I am trying to achieve the same thing for upcoming ng-toolkit version 🙈 |
Still no idea what happened, but after I restarted my computer it worked again. 🤷♂️ |
@dnalborczyk this happened after a new version was released, can you pinpoint which one? |
@dherault Did you see my PR #905 in relation to this issue? Specifically
|
@dherault I'm currently slammed at work. it'll probably take a while for me to have a look. |
The new version got released today, I will try and see how it goes as @jadams88 PR got merged too! 🚀 |
I had this problem with anything 6+, this was due to the fact that it now defaults to appending the staging name to the url path. To revert to the old way, you need to add --noPrependStageInUrl to the cli or in the serverless file custom: serverless-offline noPrependStageInUrl: true to revert to previous setting. I'm testing it his out but @dherault the functionality is not reflecting what is actually happening in AWS. i put a console.log(event.path) in AWS vs Serverless Offline
Which can break existing software as now it needs to know if prepend is on or off |
I have the same problem on routes with get |
@JimLynchCodes |
This should be fixed but turning the stage prepending off. There was already a fixed merged for the prepend #946 |
Thanks, Happy Merry Christmas,
|
This seems to be alive in v8 |
|
I have the latest version of serverless-offline installed. My Angular 9 Universal app is running smoothly locally. But I can't run it with serverless-offline. I am getting this error:
Before I updated to the latest version of serverless-offline, at least loaded the favicon. Now, not even the favicon is loading.
Here is my serverless.yml code:
Does anybody here know how to solve this issue or help me with tips of where I should be looking at? I am really lost. Without more specific errors, it's very difficult to debug.
The text was updated successfully, but these errors were encountered: