ES6

ECMAScript is the standardization of script languages, including JavaScript. ECMA stands for the European Computer Manufacturer's Association.
Here are 11,412 public repositories matching this topic...
- The users of this style guide will probably expect that all of the rules that it prescribes will be enforced by eslint. However, this is not the case - there is a secret, non-documented segmentation where some rules are enforced and others are not, because they would be "too noisy on a legacy codebase". An example of a problematic rule like this is covered in issue #2020. I propose that all of
Bug report
Given the immense popularity of Docker and the need to harden it different per platform (see ideas below) - we'd like to start writing a Docker best practices section.
You're welcome to contribute ideas and write best practices - writing and brainstorming will people is an amazing way to deepen your Docker understanding.
At first, we want to collect ideas for best practices, solidify a list
🐛 bug report
loadConfig
should emit a codeframe on a parse error:
This is for example used for loading .postcssrc
.
🤔 Expected Behavior
See screenshot in parcel-bundler/parcel#4420
😯 Current Behavior
With an invalid `.p
-
Updated
Jun 21, 2020 - JavaScript
https://eslint.org/docs/rules/use-isnan
This is a proposal to modify the use-isnan
rule.
Current rule setting:
use-isnan: "error"
Proposed rule setting:
["error", {"enforceForSwitchCase": true}]
The switch
statement internally uses the ===
comparison to match the expression's value to a case clause.
Therefore, it can never match _case NaN
. Also, `swit
This is ace, bu not really a cheatsheet as its too long form, would it be useful to actually attempt to put the same information (in short hand) on a page or couple of pages for "quick" reference? This woud probably mostly be a design challenge TBH. And happy to help
Since a lot of the categories have many articles listed, it would be helpful to highlight the top 2-4 "must read" articles in each category, if appropriate.
I should figure out how to format this, and which ones I want to highlight.
The contributing guidelines need to be fixed immediately. Issue creation guideline specially. We need to enforce adding label as one of the behaviours while creating a new issue.
cc- @tsov
If the document.domain property is set in the page, _has
module throws error "Access is denied" when try to check window's property for example 'hasOwnProperty'.
So I think it is better to change _has
module like below.
var hasOwnProperty = {}.hasOwnProperty;
module.exports = function(it, key){
try {
return hasOwnProperty.call(it, key);
} catch(e){
return
Some of the current background image selections have low contrast against the text or could be better quality images that better relate to selected verticals. This may be irrelevant if we decide to remove the image altogether.
- I've read the guidelines for Contributing to Roots Projects
- This request isn't a duplicate of an existing issue
- I've read the docs and followed them (if applicable)
- This is not a personal support request that should be posted on the [Roots Discourse](https://discourse.roots
-
Updated
Jun 24, 2020 - Go
Documentation
-
Updated
Apr 19, 2019 - JavaScript
Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.
-
I'm submitting a ...
- bug report
- feature request
- support request => Please do not submit support request here, see note at the top of this template.
-
Do you want to request a feature or report a bug?
Minor bug
loadimpact / k6
if you run
const response = http.request("get", url);
you will either:
- if http1 - get 400 (probably dependant on the implementation
- if http2 - get
WARN[0001] Request Failed error="get \"https://test-api.k6.io/\": stream error: stream ID 1; PROTOCOL_ERROR"
This is easily fixed by uppercasing get to GET
The Error is:
yarn global v1.21.0
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "C:\Users\...\npm-@babel-parser-7.9.4-68a35e6b0319bbc014465be43828300113f2f2e8-integrity\node_modules\@babel\parser\.yarn-metadata.json: Unexpected token \u0000 in JSON at position 0".
info If you think this is a bug, please open a bug report with the informati
The documentation states that this is Glide's structure, but specifically mentions adding the track attribute. So if that's required, is the HTML class structure also required or is it just for example?
<div class="glide">
<div class="glide__track" data-glide-el="track">
<ul class="glide__slides">
<li class="glide__slide">0</li>
<li class="glide__slide">1</li>
-
Updated
May 29, 2020 - JavaScript
- bizcharts Version: 3.1.5
- Platform or react version: 16.8.6
- CodePen Link: https://codepen.io/ebrahimb-the-decoder/pen/wvvNQzx
I've noticed an issue when dynamically switching axis labels on a chart. It seems that the first time the alternate axis is rendered, it ignores formatting set in the label component. Rendering the alternate a
-
Updated
Jun 12, 2019
Original issue in Nuxt.js repository:
Currently we have the following tests:
[esm/compiler-tests.mjs at a3b8290074ccd2a708ed9b985a2f89d4f4cdd026 · standard-things/esm](https://github.com/standard-things/esm/blob/a3b8290074ccd2a708ed9b985a2f89d4f4c
-
Updated
Jun 22, 2020 - JavaScript
Created by Brendan Eich, Ecma International
Released 1997
- Organization
- tc39
- Website
- www.ecma-international.org
- Wikipedia
- Wikipedia
Update various parts of the text.
There's no such thing as "early ReferenceError" anymore (for things like
0++
); they're all just "early SyntaxError" now. tc39/ecma262#691