* Add support for system property so people can launch the JVM with e.g. That engine would answer to no MIME types or filename extensions. “Nashorn ES6” allowing people to ask for an ES6 engine by name.

* Add a separate “NashornScriptEngineFactory6” class that answers to versioned names, e.g. I also have some ideas that do have legs. * specify ES6-specific filename extensions: turns out, there are none. text/javascript, application/javascript, text/ecmascript and application/ecmascript are all generic, non-versioned MIME types.

* specify ES6-specific MIME types: turns out, there’s none. Var engine = factory.getScriptEngine(“-language=es6”)īut there’s no way to do it through just using javax.script.* APIs. Var factory = new NashornScriptEngineFactory() So, the problem I’d like to solve is: using only javax.script.* API, get Nashorn ScriptEngine that runs ES6. Mostly for compatibility purposes though, it defaults to ES5 and ES6 features aren’t enabled by default. Today the most used ECMAScript version is 6 (ES6) Nashorn OTOH implements the full ECMAScript 5.1 (ES5) specification and also a subset of 6. Next message (by thread): ECMAScript 6 through the ScriptEngineManager.Previous message (by thread): What do Source, LinkerCallSite, and PropertyMap instances correspond to?.ECMAScript 6 through the ScriptEngineManagerĮCMAScript 6 through the ScriptEngineManager Attila Szegedi szegedia at

Ecmascript 6