ecma6 not supported about js-map-parser

[megaboich]

Yes, I admit. Currently extension is using https://github.com/sebastienros/jint which is EcmaScript5.1 compatible. There is a promising project https://github.com/sebastienros/esprima-dotnet which supports ES2016. But still some efforts are required to switch.

[nattlip]

Outlook voor Android<https://aka.ms/ghei36> downloaden On Wed, Dec 7, 2016 at 9:43 AM +0100, "megaboich" <[email protected]<mailto:[email protected]>> wrote: Yes, I admit. Currently extension is using https://github.com/sebastienros/jint which is EcmaScript5.1 compatible. There is a promising project https://github.com/sebastienros/esprima-dotnet which supports ES2016. But still some efforts are required to switch. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#6 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AGttxAAmWrO2nq0IcbLFHj6kzVAgHwkQks5rFnGmgaJpZM4Ka74J>.

[msamaann]

would be really nice if this plugin supported ecma6

[robert777robert777]

JINT 3.X (beta) DOES support ES6 and even some features up to ECMAScript 2020.
Any chance to build with JINT 3.X? According to jint docs it's supposed to be compatible

[chcg]

This plugin uses https://github.com/sebastienros/jint/tree/release/2.x/Jint/Parser at https://github.com/megaboich/js-map-parser/tree/master/source/Jint.Parser. Jint 3.X has no longer a own parser, but uses https://github.com/sebastienros/esprima-dotnet/tree/main/src/Esprima, see e.g. https://github.com/sebastienros/jint/blob/main/Jint.Tests/Parser/JavascriptParserTests.cs.
I'm afraid that might be no dropin replacement but needs some major adaptions.

[mlisowsk]

Well at least you can put comments around problematic code like import statements:
// jsparser:off
import * from "abc"
// jsparser:on
and the JS Map Parser will cooperate again