suitecloud 20.1 version is compatible with `19.3.x...
# sdf
a
suitecloud 20.1 version is compatible with
19.3.x
version of webstorm. You need to stay on that version. As 20.1 webstorm was released today and its a major release, they might have introduced some changes which is making the plugin incompatible. We already have plans to make the plugin compatible with newest version, but it will take time, probably till next release/e-fix.
👍 1
e
Thanks to the WS 20.1 Release Notes, TIL about the "optional chaining" and "nullish coalescence" operators, and I want them
s
I always want to run the latest webstorm (and have upgraded to 2020.1 today), but I don't see what's stopping you from using those TS operators right now in 2019.3?
e
Pretty simple
I don't use TS
s
oh. ok there's motivation for ya to use it :)
Also, aren't those operators post ES2018, so the NS runtime wouldn't support them anyway?
e
They are just proposals rn, yes. I was just stating my excitement for them. Who knows how quickly "ESNext" will keep up
s
have you seen official announcement that as of some date NS will support "ESNext" (whatever that means, since it seems these days features are individually progressed through the standards process). I do recall at the initial release of SS 2.1 they said ES2018, and that in the future they'd track ESNext?
e
I do not know the current official position on this, no, but I'd like to
From 2020.1 Release Notes:
SuiteScript 2.1 is the latest minor version of SuiteScript, ... This version is based on ES.Next, which is part of the ECMAScript specification, and it includes new language capabilities and functionality. It supports all server script types (such as user event scripts, scheduled scripts, and Suitelets). SuiteScript 2.1 and future versions of SuiteScript will also support features planned for future editions of the ECMAScript specification using ES.Next. For more information, see the help topic SuiteScript 2.1.
s
ah, very cool - I missed that. Maybe then 2.1 does have those new operators. I'll try them later
(unless you've already confirmed one way or other?)
e
I haven't tested yet. Worth a try when I get a chance. I'll report back if no one else has
s
I just tried it on a 2020.1 dev account. I get SyntaxError when trying to upload a script with either
??
or
?
operators :(
e
Yeah I've found a bunch of syntax errors on the uploader when working with 2.1
e.g. something like
{ applications, constituents, programs }
where each of those is a valid var
You can get around the parser by uploading as a zip instead of a single file
i.e. using
Advanced Add
in the File Cabinet UI
s
I didn't try that. I did try changing script in the 'edit' visual editor and uploading the file directly to FC
it does seem evident that whatever checker that runs on file upload is NOT the same as the engine itself. Things have improved but it used to be a big pain as I'd upload code I know works yet the file checker would error out.
e
Right, I've seen the same. I have resorted to always manually deploying a zip
Not ideal
Hopefully the node CLI doesn't have that issue; I've converted my current project but haven't been deploying that way yet
s
I still need to upgrade to the latest node CLI. It would be a good excuse to test single file uploads against the mysterious 'checker'.
Though, since I use TypeScript I generally do not need a checker - any syntax errors are something I'd see and resolve before even attempting to upload... so that checker is just a hindrance not a help.