PopGoesTheWza
PopGoesTheWza
Typically, a single repository composed of several projects which share common resources (i.e. code) I have this [starter template](https://github.com/PopGoesTheWza/ts-gas-project-starter) which I'll be updating for v8 support soon.
@DimuDesigns are you using the latest npm release or building directly from this repository?
A PR fixing this has been merged, so you can either wait until next release or build your own from this repository clone this repository locally and run `npm uninstall...
@DimuDesigns can you try with clasp 2.2.0 if the issue still occurs?
@DimuDesigns @kornthing Using the latest npm version of `@google/clasp` I do not experience any issue related to the `filePushOrder` in `.clasp.json` If you still are, please share a github repository...
Here is a [sample repository](https://github.com/PopGoesTheWza/clasp-filePushOrder) I used to check proper usage of `filePushOrder`. A better description in the doc may be useful though and a PR would be appreciated.
@kornthing can you please give a status about this issue?
This warning is by design and its history is difficult to track back. https://github.com/google/clasp/blob/d6fbaae5e6ad6353fe8dc9ff771c1aed1b6b1a59/src/messages.ts#L105-L108 It is always displayed with `clone`, `create` and `pull` commands, and is no longer aligned with...
Who votes it drop it? I surely do...
Just to be sure the issue still exist, can you try replacing `@google/clasp` 2.3.0 with `forked-clasp` which is more advanced? ```shell npm uninstall -g @google/clasp npm install -g forked-clasp ```