I am seeing syntax error in the SEO debug messages for a 2020.1 SCA website. The error message is:

[12:01:27.219] [    +0 ms ] Logs generated by console.log():

[    +0 ms ] SyntaxError: Unexpected token 'const'

at anonymous (<https://www.toolfetch.com/sca-dev-2020-1/extensions/shopping_2.js?t=1596211304348:466>)

I used the “const” variable declaration in the extensions code. Does the SEO Page Generator support the “const” variable declaration?

No. That’s too modern for seo generator.

OMG. you are joking. The keyword is all through the SCA code, but that code TypeScript, so the TypeScript compiler must be converting it to var. Darn it.

core typescript gets transpiled to ancient js

I have not heard the term transpiled.

all browsers support string.contains and array.contains and SEO generator does not.

Do you know if NetSuite has documented what javascript version the SEO page generator supports?

I think it’s ecmascript 5

Thanks

If you want to keep writing modern js you can try adding a transpiler to your development process, and let the transpiler target ecmascript 5 for you. https://babeljs.io/ Or code in typescript that also can transpile to that target standard. Any transpilation needs to happen in your machine before any file gets uploaded by gulp extension:deploy.

Cool. Thanks.

extensions developed by NetSuite are written in typescript, and do this. You can “get inspiration” from them.

I am guessing that they have added the babeljs.io or something similar to their development tools. Because I tried to use TypeScript early on in the 2020.1 extension development and it wasn’t supported. Then I recall seeing something on Slack about this.

they use typescript which can be addded as a npm dependency to your project and you can configure a watcher that will automatically generate a js file for each ts file on the fly on any change

Adding TypeScript to extensions is one of those things that is one the roadmap but I obviously cannot say if/when

I will. I learned my lesson. 🙂 I am not in a hurry to use TypeScript. I much prefer the require.js Define declaration to what I am seeing in the TypeScript implementation in the core code. I don’t like to see hardcoded references between modules.