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
I find it’s instructions to be lacking. I have been unable to get the example to work primarily due to the nodejs requirements. The only instruction it gives is
cd server
npm install
Which is presumptuous. The real instructions are:
ensure Node JS and npm are installed. If you don’t have those, install nvm and then use that to install the first two.
open a command prompt in the plugin’s root folder
type
cd server
npm install
And they could definitely give some troubleshooting tips for when their own packages fail to install. For example, I had permissions issues and needed to turn of strict-ssl temporarily, since I trust Adobe to not host malicious code. And then I also had to remove the existing package-lock.json because it was resolving to a private URL or something and I was getting a 401 error unable to authenticate. After all that, I was still unable to get the install to complete properly.
The text was updated successfully, but these errors were encountered:
https://github.com/sanggusti/uxp-photoshop-plugin-samples/tree/main/io-websocket-example
I find it’s instructions to be lacking. I have been unable to get the example to work primarily due to the nodejs requirements. The only instruction it gives is
cd server
npm install
Which is presumptuous. The real instructions are:
cd server
npm install
And they could definitely give some troubleshooting tips for when their own packages fail to install. For example, I had permissions issues and needed to turn of strict-ssl temporarily, since I trust Adobe to not host malicious code. And then I also had to remove the existing package-lock.json because it was resolving to a private URL or something and I was getting a 401 error unable to authenticate. After all that, I was still unable to get the install to complete properly.
The text was updated successfully, but these errors were encountered: