js-map-parser icon indicating copy to clipboard operation
js-map-parser copied to clipboard

ecma6 not supported

Open nattlip opened this issue 9 years ago • 6 comments

i get an error in vs 2015 with the map parser with "=>" in my code in ecma6 javascript

nattlip avatar Oct 19 '16 12:10 nattlip

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.

megaboich avatar Dec 07 '16 08:12 megaboich

Outlook voor Androidhttps://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 GitHubhttps://github.com/megaboich/js-map-parser/issues/6#issuecomment-265389091, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGttxAAmWrO2nq0IcbLFHj6kzVAgHwkQks5rFnGmgaJpZM4Ka74J.

nattlip avatar Dec 16 '16 23:12 nattlip

would be really nice if this plugin supported ecma6

msamaann avatar Mar 09 '20 15:03 msamaann

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

robert777robert777 avatar Nov 18 '21 13:11 robert777robert777

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.

chcg avatar Nov 19 '21 09:11 chcg

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

mlisowsk avatar Oct 31 '22 17:10 mlisowsk