I feel like I would be way faster with just conver...
# suitescript
f
I feel like I would be way faster with just converting my suitelet to a React App...
s
If I run into anything too fancy with NS Suitelets I immediately switch to building a small app where the suitelet just returns templated HTML or a small SPA.
building complex suitelets is an exercise in frustration and NS pages look rather ugly anyway
f
When you build a SPA what do you use? Like how do you pack it or do you return an IFrame and host the SPA outside of Netsuite?
s
NetSuite can host static web content in the file cabinet. Since the SPA is just static HTML/JS it worked well. Last time I did it, it was an Angular app.
I think it requires you to have the 'web store' (not SCA necessarily) feature enabled
f
I wonder If I could get webpack to bundle an AMD module and return that as a clientscript
s
would be an interesting experiment, if you really want it to be part of the NS page
when I did most of this it was pre-SS2.0
f
Maybe I give it a go one day. For now I guess for time constraints I am stuck with shitty APIs...
s
yes, not sure how often you'll be doing UI suitelets but I quickly cross the threshold where doing a SPA was less painful than doing it the SuiteScript way. However, we had already built up a general RPC-style interface for NS for apps to use, so building a SPA to invoke commands (JSON request, JSON response) was easy.
Suitelets are very limited in UI layout and capability
f
I see. Yeah I just started Netsuite dev 2 weeks ago and had to rewrite the complete plugin from previous dev...
Already very proud that I can use ES6 and have a automated development flow (save file auto updates it in netsuite etc)
s
Using ES6 via TS or just natively using ES6 because you're running only client code in a specific browser?
(or ES6 via Babel I suppose?)
n
@stalbert @fkrauthan I am in a similar situation frustrated with the lack of design options on suitelet. Just starting to explore JS frameworks and leaning towards investing time in Angular2. But before i start, i was wondering which you would recommend- Angular or React.js or Backbone.js or Extjs or Vue.js?
s
I'm planning to do my next with raw web components aka Stencil or perhaps Polymer
If I had to pick a framework for these NS apps, I'd probably choose Aurelia because it's the least intrusive - you write POJO classes and it handles two-way databinding (which is also fine for the smallish apps that tend to be build in NS)
n
interesting...
s
we've done Aurelia with NS before and it was faster and cheaper than Angular, and I assume even more so (due to less code) than React.
Polymer 3 and Stencil/Ionic are imminent.
n
wow, ive never even heard of Aurelia, im going to look into it...
f
@stalbert I use ES6 with babel transpiled to ES5 so client and server code is written in ES6
In terms of framework I personal prefer ReactJS and will give it a try how hard it is to implement. But at the end it really comes down to preference as I think all modern UI frameworks should work similar
n
Great, thanks for the input...
f
Yai I got a first prototype of a React app running as ClientScript