Does anyone know if a suitecloud.config.js's "projectFolder" is supported in WebStorm? I'm trying to deploy from a "dist" folder but it only seems to want to install from the src folder.

I get the feeling that setting is just for the 'project root' - i.e. doesn't control what gets deployed or from where.

deploy.xml

controls where things are deployed from, and the path must start with

~/FileCabinet/

or

~/Objects/

or whatever the default value is for the object type you're deploying - below that default you can organize and deploy how you see fit, but you can't use anything above the default, afaik

@stalbert, @erictgrubaugh - Thank you. I'm trying out Typescript and wanted to compile into dist but I can do it the other way round and compile into src.

I've been using TS for years with SuiteScript - and what's worked well for me is to just put my TS files in the natural location under

FileCabinet/SuiteScripts

and let TS output the

.js

files right alongside the

.ts

files. I also recommend uploading both the

.ts

and

.js

files to file cabinet, just in case.

This file is is supported in Node CLI for now. In future WS might use that. @Chris Abbott The use case you are describing is possible in nodecli. you can create a workflow to Transpile from 1 directory and deploy from a different directory

dist

for example.

@Ali Syed (NS DevTools QA) - Got it, thank you. It's currently being included in a project created in WebStorm though which is a little confusing.

Yes this is because if you create a project in WS, you can still use it in NodeCLI. For example a user might want to create a project in WebStorm, and uses WS terminal to use nodeCLI also (Or any other terminal).

@Ali Syed (NS DevTools QA) - OK. Understood.