1. 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

Was checking babel/babel#11478 and testing out syntax and noticed we don't error with the normal "use this plugin/preset" like we do for proposals with JSX itself. @nicolo-ribaudo mentioned it's probably since jsx is implemented as a normal plugin so we didn't have `this.expectPlugin("recordAndT

🐛 bug report

loadConfig should emit a codeframe on a parse error:

https://github.com/parcel-bundler/parcel/blob/2f6274311889cad76fbdf2dafe60fc23478476d6/packages/core/utils/src/config.js#L80

This is for example used for loading .postcssrc.

🤔 Expected Behavior

See screenshot in parcel-bundler/parcel#4420

😯 Current Behavior

With an invalid `.p

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

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 

Describe the issue / bug.

I added these configs in launch.js,

After F5 debug, already vscode debugging child processes.

but, breakpoint in main process used in folder

Steps to reproduce

1. Starting at URL: wordpress.com/post
2. Click Jetpack icon for site with broken LinkedIn connection

What I expected

Nicely formatted text

What happened instead

Browser / OS

This would be a nice little feature to have, Excel users are using this a lot.

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>
  

The documentation here incorrectly states, "This will mangle all properties that start with an underscore." when in fact the provided example will mangle all properties that END with an underscore.

Original issue in Nuxt.js repository:

• esm() breaks console.*() functions in esm-styled nuxt.config.js · Issue #6808 · nuxt/nuxt.js

Currently we have the following tests:

[esm/compiler-tests.mjs at a3b8290074ccd2a708ed9b985a2f89d4f4cdd026 · standard-things/esm](https://github.com/standard-things/esm/blob/a3b8290074ccd2a708ed9b985a2f89d4f4c

I couldn't find any place in the documentation that would showcase all possible configurational parameters that can be used inside backpack.config.js file. Is it possible to add not only config.entry.main but also showcase all other available options with a brief explanation of its purpose?

I'm testing out madge on my TS RN codebase, and I'm surprised to see that it just magically works without specifying a tsconfig.

For example
yarn madge --circular --extensions ts,tsx ./

Although this is cool and exciting, it gives me pause because the documentation doesn't explain how this works. I read the source and followed the path through a series of external npm dependencies. Af

嗨, 您好
在學習CH05的時候,遇到一個問題
發現在 webpack.config.js 裡面的 module: { preLoaders: [ { ... } ],
似乎造成webpack錯誤 無法執行

如下terminal截圖

稍微查了一下,解決方法是用 webpack@2.1.0-beta.22 版本
我目前是 "webpack": "^2.2.0", _應該也

I am using JsBarcode to make a barcode scanner programming sheet for our application. Our barcode scanner adds some unusual Code128 symbols at the start to make sure that regular barcodes do not cause it to change its settings. For our scanner the programming codes are always in format: START B, FNC3, programming code, STOP.

Forcing Code128B is well documented, but inserting the FNC3 symbol (

I was trying to look up the API for the DebugPanel so I could locate an option to decrease the text size. I'm developing a smaller resolution game and the elements of the panel overlap and are unreadable/unusable at these lower sizes. Upon opening the API and searching/clicking on the DebugPanel link, I'm routed to [http://melonjs.github.io/melonJS/docs/me.DebugPanel.html](http://melonjs.github.io

The features section in the docs states that nodemon is available in the project, when it's clearly not. It's not added as a dependency or as a command in the project. Maybe remove this from the docs or actually add nodemon?