Hi all, I got error which i have no clue what's wr...
# sdf
d
Hi all, I got error which i have no clue what's wrong, it's upon adding dependencies
Copy code
PS D:\eclipse_workspace\myproject> suitecloud project:adddependencies       
Project folder "D:\eclipse_workspace\myproject"  -all" does not exists.
Please help
a
Uh, this looks weird 😞
Can you create an issue in GitHub?
a
This is working fine for me. Can you provide an actual screenshot of the command you executed and the output @dennysutanto
d
here, i'm using vscode
a
can you show your
suitecloud.config.js
file?
d
@Albert Margarit (NS Eng Lead) here
a
can you remove the override of project path in adddependencies?
d
this part ? "project:adddependencies": {         projectFolder: './',     },
a
yes
d
this is my current suitecloud.config.js
module.exports = {
  
defaultProjectFolder: "./",
  
commands: {
    
"project:validate": {
        
projectFolder: 'dist',
    
},
    
"project:deploy": {
      
projectFolder: "dist",
    
},
  
},
};
Still same error PS D:\eclipse_workspace\Fabelio> suitecloud project:adddependencies Project folder "D:\eclipse_workspace\Fabelio" -all" does not exists
a
and if you remove:
Copy code
defaultProjectFolder: './',
d
wow it works
so what does this line do actually ?
Copy code
defaultProjectFolder: './',
@Albert Margarit (NS Eng Lead) I'm using @Brendan Boyd workflow to do deployment, where i copy all changed files to "dist" folder and deploy from there, I'm not really sure though if by removing that line above will impact the deployment
i will try in sandbox first
btw @Albert Margarit (NS Eng Lead) thanks for pointing out on the issue
a
maybe if you change that line from "./" to "/" it will work?
that line just says that the project folder is at the root. Which it's a bit redundant because if you don't specify it, it will always take the root
d
ok thanks @Albert Margarit (NS Eng Lead) will give it a try
b
@dennysutanto attached is the updated package.json and suitecloud.config.js I'm using for the suitecloud cli.
The
npm run deploy:staged
task is the only one currently using suitecloud cli, but you should be able to pick that apart if you have other needs.
The only reason I'm still using the package.json tasks is for building the dist folder, and I haven't tested it completely in our CI process. At some point it will probably all go into the suitecloud.config.js file...
d
thanks for the files @Brendan Boyd
👍 1
The other day i had an issue running npm run deploy:staged in windows, but i couldn't remember exactly on the error, basically all the deploy:xxx didn't work
it worked perfectly on mac
if i remember correctly it's something related to the rm , mkdir command, like they are not avaialble in windows
b
ya, those are all unix commands
they will only be available on windows if you install WSL 2.0