Exporting Projects

platforms/ and node_modules/ are large, machine-specific and rebuilt by the CLI anyway, so move only what you wrote (www/, res/, config.xml, package.json, package-lock.json, scripts such as r) and restore the rest where the project lands:

du -sh platforms node_modules
tar -czf ../booknest-export.tgz --exclude=./platforms --exclude=./plugins --exclude=./node_modules .
ls -lh ../booknest-export.tgz
mkdir ../booknest-moved && tar -xzf ../booknest-export.tgz -C ../booknest-moved
cd ../booknest-moved
npm install
cordova prepare

29M   platforms
20M   node_modules
-rw-r--r-- 1 dev dev 91K Sep 25 05:19 ../booknest-export.tgz
...
added 178 packages, and audited 179 packages in 2s
...
Discovered platform "android". Adding it to the project
...
Discovered platform "browser". Adding it to the project
...

49 MB of generated folders became a 91 KB archive; npm 2,036 install fetched the pinned packages, and cordova prepare recreated the platforms and plugins named in package.json. Git 1,932 does the same with less ceremony: the .gitignore from cordova create leaves the generated folders out, so a clone followed by npm ci and cordova prepare rebuilds the project. Keep the upload keystore (Upload Keystore) out of both.