This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Anyone using JEST is a SuiteApp SDF project.  I can seem to get the import paths correct I'm my tests.  The examples is the GitHub project are incomplete and only showcase Account Customization projects

you could look at the NFT unit tests for an alternate but similar approach (and it's a known working overall configuration for jest and netsuite)

So, I discovered something.  Because I'm using TypeScript, my exports are directly against the `exports` object (there is no RETURNed object).

This is 'one' of the issues I'm having.  <@U5375UUJ2>, is there a way to have the typescript compiler add that to the output?

add _what_ to the output? Oh wait - what I do to make Jest testing easy is to compile to UMD format.

That emits code that works in both AMD (netsuite) or CommonJS (node/jest)

I added this at the end of my Typescript file (Restlet)

```export = {get : get};```
The compiler complains, but it spits out the `return` object like I want it

but yes that's a good point - we've used the `export =` syntax for years though I know it's now discouraged

by the way, you could also just export the top level items directly

we don't because we put things in a namespace first to give something for `autoLogging` to grab onto

e.g. `export function get(){}` instead of `export = {get:get}`

The problem there is, the generated module does an `exports.get = get;`  when I need a `return {get : get}`

if you compile for UMD it should return when it needs to and assign to exports when it needs to - i.e. work in both scenarios