sp.search.js and search.clientcontrols.js missing

[SPWizard01]

is there any specific reason this is missing?

my use case is to import search configuration.

[koltyakov]

Hi @SPWizard01,

No any particular reason.
Added, but can't test at the moment. Could you please try (sp-jsom-node@2.1.0)?
search should be explicitly added in the modules list.

const jsomSettings: IJsomNodeSettings = {
  modules: [ 'search' ]
};
new JsomNode(jsomSettings).init(authOptions);

[SPWizard01]

something got messed up :D
(node:26780) UnhandledPromiseRejectionWarning: RangeError: Maximum call stack size exceeded
at Function.Object$getType [as getType] (C:...\node_modules\sp-jsom-node\jsom\spo\msajaxbundle.debug.js:450:38) and its only when i add search as dependency

i will investigate, oh and by the way "search" type is missing, typescript will complain :)

[koltyakov]

He he, was over optimistic to expect it works so easy.
Any investigations are appreciated. Thanks!
I’ll take a deeper look and add tests as well over the weekend.

[SPWizard01]

ok, so i got it to work partially, without search.clientcontrols.js

sp-jsom-node/src/JsomNode.ts

Line 162 in 1b243f6

registerNamespace('PS');

had to add this:
registerNamespace('Microsoft.SharePoint.Client.Search'); registerNamespace('Microsoft.Office.Server.Search');

now if i add:
registerNamespace('Srch'); <- this is all in search.clientcontrols.js it will the no longer give me maximum stack but rather cannot read property of undefined in here:

sp-jsom-node/jsom/spo/search.clientcontrols.debug.js

Line 9612 in 1b243f6

var $htmlEncode = SP.Utilities.HttpUtility.htmlEncode;

so i wonder how its possible because it should be available from:

sp-jsom-node/jsom/spo/sp.init.debug.js

Line 1303 in 1b243f6

SP.Utilities.HttpUtility.htmlEncode = function SP_Utilities_HttpUtility$htmlEncode(str) {

[SPWizard01]

and if we add sp.init.js to dependencies it fails here:

sp-jsom-node/jsom/spo/sp.init.debug.js

Line 1401 in 1b243f6

ListContext.registerClass('ListContext');

[koltyakov]

I was managed to make it work. Please check just published v2.1.1
However, search.clientcontrols.js is still limited (SP.Utilities.HttpUtility is faked as an empty object) and I can't recall what was the issue including sp.init.debug.js.
Could you also elaborate on your use case of search.clientcontrols.js in Node.js app? Hands itching soo much to exclude search.clientcontrols.js.

[SPWizard01]

i think you are right, this one is only for UI interactions(or so it looks), at least my use case is working without it, bad assumption from my side then :)

[koltyakov]

So I likely remove search.clientcontrols.js in the next version. Also considering it's only for UI part.