ecmascript-next

I'm trying to use decorators in my JS project, however ESLint is throwing an error stating that the @ symbol is a unexpected character. My code: @observable items = []; My .eslintrc: { "parserOptions": { "ecmaVersion": 6, "ecmaFeatures": { "jsx": true }, "sourceType": "module" }, "env": { "browser": true, "node": true, "es6": false }, "ecmaFeatures": { "modules": true }, "rules": { "strict": [ 2, "global" ], "quotes": [ 2, "single" ], "indent": [ 2, 4 ], "eqeqeq": [ 2, "smart" ], "semi": [ 2, "always" ], "max-depth": [ 2, 4 ], "max-statements": [ 2, 15 ], "complexity": [ 2, 5 ] } } You

I've come across the term "ESNext", and wondering it is same as the EcmaScript. So, I have these questions here: What is ESNext, actually? Does it refer to any specific version of EcmaScript? What is ESNext, actually? It varies depending on who's using the term, usually "the next" version of ECMAScript (JavaScript). For instance, at this moment if someone said "ESNext" they might be talking about ES2019 plus BigInt, dynamic import, and other features that recently reached Stage 4 of the process , or they might even be talking about those plus some advanced Stage 3 proposals. Does it refer to

This question already has an answer here: Using async/await with a forEach loop 15 answers Given the following code class SomeClass { async someFunc() { const urlParameters = [0, 1, 2]; const batchAjaxResult = await urlParameters.map((parameter) => { const result = await $.get(`someUrl/${parameter}`); return { parameter, result } }); console.log(batchAjaxResult); } } JavaScript will return an Array of resolved Promises instead of the actual Promises result. This is probably due to Array.map() not being implemented as a Promise. Is there a Promise-based version of Array.map ? This is question

I have the following setup: { "babel-core": "~5.8.25", "babel-eslint": "^4.1.3", "babel-loader": "~5.3.2", "babel-polyfill": "^6.2.0", "eslint": "^1.7.3", "eslint-config-airbnb": "^0.1.0", "eslint-loader": "~1.1.0", "eslint-plugin-angular": "~0.12.0", // ... } webpack: module: { preLoaders: [{ test: /\.js$/, exclude: /node_modules/, loader: 'eslint-loader'}], loaders: [ { test: /\.js$/, exclude: /node_modules/, loaders: ['ng-annotate', 'babel-loader?plugins[]=transform-decorators-legacy'], } ] } But I get the following error: TypeError: The plugin "transform-decorators-legacy" didn't export a

I'd like to inject lodash by name, something like this: let val = function(lodash){ // lodash will be injected, simply by using require('lodash'); }; but say I want to rename the import, I want do something like this: let val = function({lodash:_}){ }; or let val = function(lodash as _){ }; is there a way to do this with either ES6/ES7/ES8 or TypeScript? Note that this DI framework does more work than just require('x')...it will try to inject other values first, if nothing else exists, then it will attempt to require the value. Note also that the requirements here are that when you call val

Is there a cleaner way to do this (with anything that is at least an ES draft and has a babel plugin, i.e., ES6, ES7, etc.): const { a, b } = result = doSomething(); Where I want to keep the overall result as one singular object, but also destructure it at the same time. It technically works, but result is implicitly declared (with an implicit var ), while I'd really like it to also be a const. I'm currently doing this: const result = doSomething(); const { a, b } = result; Which again works, but it's slightly on the verbose side, since I need to repeat this pattern dozens of times. I'd