package.json of our samples are polluted by our maintenance tools

Take a look at this example: https://github.com/GoogleCloudPlatform/nodejs-docs-samples/blob/master/appengine/hello-world/standard/package.json

cloud-repo-tools, devDependencies and most of the scripts do not serve the purpose of giving example code to our users, instead, they are data used by our maintenance tools.

Could they be in a different file that does not interfere with package.json ?

[fhinkel]

A lot of samples rely on this test setup:

"cloud-repo-tools": {
    "test": {
      "app": {
        "msg": "Hello, world!"
      }
    },
    "requiresKeyFile": true,
    "requiresProjectId": true
  }

If we remove the repo-tools dependency, we’d need to write those tests ourselves - which I would prefer because no user will be familiar with the repo-tools magic.

[fhinkel]

Closing this, I think our package.jsons are fairly standard and not confusing to Node devs.