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

I know its probably more advanced then what most people need. But in my case I try to pack a reactjs single page app as a clientscript and had to spend quiet some time to find a working workaround

FYI what I’ve done to work around this issue is have a standard client script that loads my webpack’d script as a module

Interesting. I've actual created a workaround too with webpack. Its based on the wrapper plugin but heavily modified to support imports of Netsuite modules

Ah yes I used the wrapper plugin as well to prepend a JSDoc that specifies `NAPIVersion` and `NModuleScope`. That plus a updating the webpack config so that it knows that all of the N/* modules are externally available over amd

```{externals: {"N/record": {amd: "N/record"}}}```

I’m using the `@hitc/netsuite-types` npm module with TypeScript so this snippet does it for me:

```const externals = {};
    fs.readdirSync(path.resolve(context, "node_modules/@hitc/netsuite-types/N")).forEach(function (file) {
      if (file === '.' || file === '..') return;
      const module = 'N/' + file.replace('.d.ts', '');
      externals[module] = {amd: module};
    });```

My trick is ```plugins: [
        new WrapperPlugin({
            header: function (fileName, externalDependencies) {
                return `
/**
 * @preserve
 *
 * @NApiVersion 2.x
 * @NScriptType ClientScript
 */
define([${Object.keys(externalDependencies).map(d =&gt; `"${d}"`).join(",")}], function(${Object.values(externalDependencies).join(",")}) {
    ${NETSUITE_GLOBAL_SHIMS.map(shim =&gt; `
    if (typeof(${shim}) === "undefined") {
        ${shim} = {};
    }
    `).join('')}
                `;
            },
            footer: function () {
                return `
    return {
        pageInit: NetSuiteSSP.pageInit,
    };
});
                `
            }
        })
    ]```

And I compile the project as ```output: {
        filename: '[name].bundle.js',
        library: 'NetSuiteSSP',
        path: path.resolve(__dirname, 'dist')
    }```

And I modified the existing `WrapperPlugin` a bit to give me a list of external dependencies and define externals like you did for all netsuite dependencies

Oh gotcha. Yeah I can see how that works. Cool!

The cool thing is I can add a import to any netsuite dependency anywhere in my codebase and its going to work correctly

while not having to use custom AMD modules or anything like that

Yeah totally. I have mine defining all of the external modules in case they come up so I don’t need to worry about it either ;)