You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any reason why this isnt simply a CLI tool on npm? Also why the explicit calling of node? This is kind of counter-intuitive to people coming from the web ecosystem.
I would also suggest having the user optionally explicity provide the config as it confused me and it seems to confuse others too (judging by the forum and issues).
A more usual / preferred developer experience would be:
npm install playcanvas-sync -g
playcanvas-sync -c my-config.json watchAll
The text was updated successfully, but these errors were encountered:
After 'npm install' from the project folder you can run it without 'node' or '.js'. The example command in the readme is for less experienced users who may not want to install it. './pcwatch.js' would also work.
Any reason why this isnt simply a CLI tool on npm? Also why the explicit calling of node? This is kind of counter-intuitive to people coming from the web ecosystem.
I would also suggest having the user optionally explicity provide the config as it confused me and it seems to confuse others too (judging by the forum and issues).
A more usual / preferred developer experience would be:
npm install playcanvas-sync -g
playcanvas-sync -c my-config.json watchAll
The text was updated successfully, but these errors were encountered: