What ever happendd to our idea of moving to Dicord? I find more and more of the communities I frequent are there, for better or worse?

I think that idea, started due to licencing cost here, but it’s already a pretty big community now(13k), so it might be hard to move all the people, but it can be done overtime for sure. Can’t we just go and start a new server there?

It shouldn't be hard to move users - you just shut one system down leaving a link to the new system. I personally like the Slack UI (never though I'd say that) more than Discord, but if their FREE tier allows us more capability than we get here, I don't know why we wouldn't do it. Both platforms are very popular.

If it were Discord we could have searched 😄 where is that poll?

In any case, I'm kinda stuck using both Slack and Discord anyway, but noticed that this slack org is the only 'community' one I have any more. Clients still require Slack from time to time but most of my other 'official community' chat channels all seem to be over on Dicord (e.g. TypeScript, PrimeFaces, Angular, Deno, etc)

I got to know about three new things, PrimeFaces, Deno and Playwright. Thank you

We do use two of them with NS work - PrimeFaces (PrimeNG in particular) and Playwright (for testing web apps and RESTlet/Suitelet based APIs). Deno, not so much for NetSuite.

Do you build custom UIs in NS using PrimeNG? I have seen people using React and VueJs so far, but that’s interesting. I do testing by myself in Postman or in UI for restlet/suitelet, how is Playwright better than that?

I would have preferred discord as well. But the current discord for Netsuite is kinda dead.

Playwright is 'better' for a few reasons 1. no dependency on an external tool (i.e. postman) 2. The tests are just typescript code - so you can debug them, do assertions, logic, etc. 3. the tests are easily checked into version control since they are just code. with postman, you could checkin a collection but that's disjointed from the rest of the code. 4. Playwright lets you manipulate the web pages with automation. For example, you could have a test 'login' automatically before invoking the RESTlet/Suitelet so that it runs as a specific user. This is, in fact, the primary use case for Playwright. 5. It lets us use the same tool for both API testing AND e2e web testing.