Hello David

Glad to know that you resolved the issue. From my research, I didn’t find 
any evidence / documentation that lead us to believe that cd’ was 
officially supported before. As mentioned in the documentation you 
referred, you can find the current supported packages in this 
<https://cloud.google.com/appengine/docs/standard/nodejs/reference/system-packages>
 
link as well as you can request to include new packages from this issue 
tracker link <https://issuetracker.google.com/issues?q=componentid:441254> 
if there is no existing request for that.

On Friday, November 2, 2018 at 3:33:02 AM UTC-4, [email protected] wrote:
>
> The start command above was the only script changing path we used. For now 
> we solved it by removing the cd command altogether by restructuring our 
> folders.
>
> {
>  ...,
>  "scripts": {
>    "start": "node -r ./ts-paths.js dist/src/server.js"
>  }
> }
>
> I checked the available system packages in the documentation and noticed 
> *cd* is not part of them.
>
> https://cloud.google.com/appengine/docs/standard/nodejs/reference/system-packages
>
> Could it  be never officially supported and got removed altogether on the 
> day our app broke?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cc4e87c3-6f65-4059-aab1-d36e8dc11465%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to