My Stuff
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
Comments
-
Hi Bry, The upload was successful! Thank you so much for the help! Last question: If we need to revert back to the version previous to this, what's the easiest way to do so?
-
Hi Bry, Both are done, and I now got passed the dependencies! Thank you so much! I have a new error during deployment, see the screenshot below: The consumer key and secret are in place I believe, but it's throwing a permission error on my end. What does this mean? And how can I resolve this?
-
Hi Bry, I have installed the said node and npm version on my machine: I also installed the fix applied previously after doing the npm install: But now I got this error: This is the first time I saw this error. Can you check what's this about and suggest a solution for it?
-
Hi Bry, Thank you for the file shared. Here's what I found: I ran gulp deploy, and encountered this new error: Does this mean it's incompatible with my operating system? I looked up the error online, and it suggested to rebuild node-sass, which wasn't successful on my end: Please let me know how to proceed with this. For a…
-
Hi Bry, Thank you for the detailed instructions. Here are my findings with the steps provided: my gulp version is aligned to your recommendation I have updated the old node modules to be a backup on my end. The other one was the newly created: After running npm install, I still got the node-sass error previously reported:…
-
Hi Bry, I was able to install gulp-sass 2.1.0 now: Only node-sass 3.9.3 is left. It is still erroring out when attempting to install it directly with npm: Hopefully this gives insight on your end.
-
Hi Bry, Thank you for the files. I was able to verify that there were a lot of missing files from that folder to the backup that I have, and have added them in! I tried running gulp deploy now, but I encountered the same error: I have followed the previous instructions when we first had this error, and made sure that in…
-
Hi Bry, Upon checking, there isn't so I created one with the given content you mentioned. Thank you for that! Before I run gulp deploy, are there any other files that I need to validate first before running it? Like the templates within the suitetalk4node? That way I can avoid posting the same error for a missing file, and…
-
Hi Bry, Good catch. Thank you, but it seems to still be persisting: Do you have any insights on this?
-
Hi Bry, Thank you for the files. I've replaced them, and ran npm install, and here are the results from it: Here are the results from the last 2 commands to install: When running gulp deploy, here's what I got: It looks like an error pointing to gulp-ttf2woff, but didn't encountered any issues during its installation. Can…
-
Hi Bry, Thank you so much for the help, you are more helpful than the Support Team with this. I have encountered a new error when testing using "gulp local": I believe I installed everything correctly, and have replaced the files as mentioned. Can you advise if there are any steps that I need to take?
-
Hi Bry, Checking the package.json file, the said is there: I also checked that directory, here's what it has: Is there a file missing on my end? And if it is, how will I be able to retrieve that file?
-
Hi Bry, That seems to work, as I was instructed to run npm install now. Thank you! The problem is, I'm getting this new error: The package.json file is in the folder where the terminal is running on: What seems to be the problem here?
-
Hi Bry, Thank you so much for answering. I'm close to getting it done, but unfortunately, following the steps didn't work for me. Here's where I got a roadblock: Upon installing gulp and trying to deploy it, I'm greeted with the following error: It seems to be looking for a newer version of node, while your instructions…
-
Hi everyone, We can close the thread. This is already resolved from my end. Thank you for the help!