Change in .clasp.json location & behavior with --rootDir

Steps to reproduce the problem

1. Install clasp locally
2. Create a project using --rootDir
3. Attempt to push files

Expected Behavior

(as in 2.4.😇 4. Success

% mkdir -p project-2.4.0/{src,tools}
% cd project-2.4.0/tools
% npm install @google/clasp@2.4.0
...
% ./node_modules/.bin/clasp create --type webapp --title test-2.4.0 --rootDir ../src
Created new webapp script: https://script.google.com/d/.../edit
Warning: files in subfolder are not accounted for unless you set a '.claspignore' file.
Cloned 1 file.
└─ ../src/appsscript.json
% ./node_modules/.bin/clasp push
└─ ../src/appsscript.json
Pushed 1 file.

Actual Behavior

(in 2.4.1:) 4. .clasp.json file (now in rootDir rather than same directory) not found; must run with clasp -P rootdir

% mkdir -p project-2.4.1/{tools,src}
% cd project-2.4.1/tools 
% npm install @google/clasp@2.4.1
...
% ./node_modules/.bin/clasp create --type webapp --title test-2.4.1 --rootDir ../src   
Created new webapp script: https://script.google.com/d/.../edit
Warning: files in subfolder are not accounted for unless you set a '../src/.claspignore' file.
Cloned 1 file.
└─ ../src/appsscript.json
% ./node_modules/.bin/clasp push   

No valid /Users/chjones/Downloads/project-2.4.1/tools/.clasp.json project file. You may need to `create` or `clone` a project first.
% ./node_modules/.bin/clasp -P ../src push
└─ ../src/appsscript.json
Pushed 1 file.

Specifications

• Node version (node -v): 16.5.0
• Version (clasp -v): 2.4.1
• OS (Mac/Linux/Windows):Mac

Presumably this is associated with #865 ; the new behavior may be the “correct” one, but failure to create .clasp.json in the working directory is a breaking change when that is expected (at least, for some of my scripts. 😃 ) Is this worth specifying in documentation or release notes?

Thanks as always, CDJ

[therealchjones]

Additional issue: as the relative directory rootDir is also written to .clasp.json as given to the --rootDir option., clasp -P must also be called from a directory at a certain hierarchy.

From the above, if we are in the tools directory and use clasp create ... --rootDir ../src to place the project in the given src directory, ../src is written to .clasp.json, hence moving up a directory level and calling clasp -P src/ ... results in:

% clasp -P src/ push
ENOENT: no such file or directory, open '../src/appsscript.json'

If we can agree on desired behavior for --rootDir and -P I’m happy to work on a PR. Thanks again!

[tresorama]

I figured out that:

1. clasp push need a .clasp.json to know what to do.
2. clasp create ... --rootDir ./dist create .clasp.json automatically and store it at ./dist/.clasp.json
   • BUT IF ./dist DIRECTORY DOES NOT EXIST CLASP WON’T CREATE THE FILE.

IF YOU ARE CREATING A NEW PROJECT

( Google Sheets as Container in this example )

It’s better you initialize the project with :

cd ~/Desktop
mkdir my-gas-project
cd my-gas-project
clasp create --type sheets --title "MySheetsContainer" --rootDir .

This let clasp create the .clasp.json in the current working directory.

Then, assumed your code bundler (ie. webpack ) put your code inside ./dist, you need to manually update the .clasp.json :

{
  "scriptId": "1AFqeTOrlAA7TjcbAuW9Pqt_cxPVliUfeagV1YDS9WNHJK62RD8G2Lwt0",
  "rootDir": "./dist",  // <- HERE PUT YOUR BUNDLE DIRECTORY
  "parentId": ["1lViSwkMtrnJcYSvi9NcvmO2OamJzgXz_dUoXNn0SxVQ"]
}

IF YOU’VE ALREADY CREATED A PROJECT

In this case you should not have the .clasp.json file.

So create .clasp.json and put in project root directory , or the directory from where you call clasp pull | push:

{
  "scriptId":"1AFqeTOrlAB7TrcbAuW9Pqt_cxPVliUfeagV1YDS9WNHJK62RD8G2Lwt0",
  "rootDir":"./dist", // <- HERE PUT YOUR BUNDLE DIRECTORY
  "parentId":["1lViSwuMtrnJcYHvi9NcvmO2OamJzgXz_dUoXNn0SxVQ"]
}