Is your feature request related to a problem? Please describe.
I noticed, when reviewing freeCodeCamp/freeCodeCamp#38016, that a lot of HTML was necessary to create challenges that looked good (freeCodeCamp/freeCodeCamp@7b9db26#diff-8d5114b548781516c78ac91bc507f8ebR14, for instance). While using HT

What problem does this feature solve?

I just spent way too long debugging something really weird until I realized I accidentally wrote :v-if instead of v-if.

A warning when wrongly using shorthands like : on "native" vue attributes could prevent this bad experience easily.

What does the proposed API look like?

:v-if="foo"

--> console.warn("You specified v-bind:/ v-on:

https://twitter.com/therealyashsriv/status/1219691914523545601

We shouldn't generate code that might cause browser or linting to complain.

https://github.com/facebook/react/blob/0cf22a56a18790ef34c71bef14f64695c0498619/packages/legacy-events/SyntheticEvent.js#L259

It's also just a confusing pattern at best.

Wasn't sure quite where to report this, but it appears your HTML <blockquote> example isn't technically correct:

<blockquote class="blockquote">
  <p class="mb-0">Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer posuere erat a ante.</p>
  <footer class="blockquote-footer">Someone famous in <cite title="S

Chapter in question: https://github.com/getify/You-Dont-Know-JS/blob/master/es6%20%26%20beyond/ch2.md#template-literals

The suggestion seems to be that the template literals would be all about strings; there's only examples that result in strings, and phrases like "final string value" and "generating the string from the literal" are used in what should be a general context, but the tag function

The max-classes-per-file rule is enabled in rules/best-practices.js but there is no mention of this requirement in the docs. If this is a best practice, I'd like to know why.

Consider the following snippet run in the main process where one wants to listen for "will-prevent-default" events and after some asynchronous operation (do_something, a call which returns a Promise) initiated by the event listener, depending on the result (result) of the operation, call preventDefault on the even

Section/Content To Improve
Section "Config order of precedence".

Suggested Improvement
The current implementation of

When not using a file extension in ESM - eg import pkg from './path' we currently just throw a straightforward not found error. As proposed by @MylesBorins in nodejs/modules#443 it would be useful to enhance this error message.

Ideally the error message should run the CJS resolver and say "the CJS resolver would have resolved this module to ...". We actually previous

Huge and nice collection and also getting very much appreciated from the community.
It would be great if somebody can translate into English then it will be reaching out to global.

https://github.com/trekhleb/javascript-algorithms/blob/master/src/algorithms/sets/cartesian-product/cartesianProduct.js#L8

I think it makes more sense to return an empty array

// invalid input return null or throw an error
if (!setA || !setB) {
    return null;
}
if (!setA.length || !setB.length) {
    return []; 
}
// or do nothing since the for loop will not trigger anyway

The deprecated decodeDracoFile method should be removed and replaced with a parse method similar to other loaders. Currently decodeDracoFile does not propagate errors, and should do so. So probably a signature like:

dracoLoader.parse( arrayBuffer, /* options, maybe? */, onLoad, onError );

Search Terms

• return type quick fix
• async function quick fix
• global promise type

Suggestion

It would be nice if TypeScript contributed a quick fix to resolve The return type of an async or global function must be the global Promise<T> type errors. The fix would simply wrap the existing return type into a Promise.

Checklist

My suggestion meets these guidelines:

https://angular.io/events

Description

So our function arrayToHtmlList is in a pretty bad space and could use an update. We already had some discussion over at #675 but I wanted to move the update discussion over to an issue for more visibility.

Current problem:

It uses an awkward query selector instead of the `document.prototype.getElementBy

• The issue is present in the latest release.
• I have searched the [issues](https://github.com/mui

Feature request

Support optionalDependencies as NPM and Yarn do:
http://npm.github.io/using-pkgs-docs/package-json/types/optionaldependencies.html
https://yarnpkg.com/lang/en/docs/dependency-types/

It's useful for example when you need to use an package in Windows and other in Mac/Linux and packages support os t

Prerequisites

• Put an

If you follow the readme procedure, the following error will occur in the first npm install express.

saveError ENOENT: no such file or directory, open '/xxx/xxx/package.json'

As you know, the cause is package.json does not exist.
Other users seem to have a similar error, so it seems better to add npm init to the readme.
Or I thought it would be nice to bring a link `Please follow

Documentation Is:

• Missing or needed
• Confusing
• Not Sure?

chartArea node has been changed into v3

The chartArea node of a chart adds width and height properties, comparing with version 2.9.3.

Add into doc for migration 3

At the moment this change is not documented into migration 3 doc

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://storybookjs.now.sh/official-storybook/?path=/story/addons-jest--with-tests'
   in a narrow width browser.
2. Click on the Tests panel.
3. Scroll down to see the tests panel.
4. See the total number of tests and total time covering up the "Todo" tex

Existing Component

是

Component Name

el-table

Description

Hi, I found that some documents are still using slot and slot-scope. In Vue 2.6.0, it is use v-slot, your can see vue document here https://vuejs.org/v2/guide/components-slots.html.

Example:

<el-table-column
      fixed="right"
      label="操

where to declare .d.ts? 1.8.2

Package.describe({
  name: 'gooodrr',
  version: '0.0.1',
  summary: 'gooodrr',
  documentation: 'README.md'
})

Package.onUse(function (api) {
  api.use('typescript')
  api.mainModule('gooodrr.ts', 'server')
  api.export('Gooodrr', 'server')
})

where to put d.ts file?

declare module "meteor/gooodrr" {
    export module Goood

Bug Report

Ionic version:

[x] 4.x

Current behavior:

When you navigate from a tab page to another tab page and then go back with the ion-back-button, you will always end up at tab index 0 of the first tab page.

Expected behavior:

Instead, the app should go back to the tab where the user came from.

Steps to reproduce:

To illustrate the problem, I have ta

🎉🎉 The Node.js best practices guide has gotten even better during September and October, thanks to the many awesome contributions made by the following folks 🎉🎉

📢 🇷🇺 Our guide is now also translated to Russian (+ other 8 languages)! This thanks to the AMAZING work of Alex Ivanov @contributorpw ❤️

The following folks suggested & contributed great new ideas and enhancements:
🌻 Adeel Imran @A

Do you want to request a feature or report a bug?
feature request

What is the current behavior?
Currently yarn why won't indicate any package info in the resolutions field

If the current behavior is a bug, please provide the steps to reproduce.

1. install a package with any version, e.g "pkg": "^1.0.0"
2. add resolutions field in package.json, pkg: "1.0.0"
3. upd

The Head section says:

The next 2 meta tags (Charset and Viewport) need to come first in the head.

I found a reference for Charset being early on in the head:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta

The <meta> element declaring the encoding must be inside the <head> element and within the first 1024 bytes of the HTML as some browsers only look at those bytes be

Hi, I have been spending quite sometime wondering why a simple dropdown was not working.
Is not specified on the docs that the must have the class 'dropdown-trigger' (any other is not triggering the dropdown!)

Just a matter of documentation but crucial in order not to waste time :.)
example, this will not work:

<a class='dropdown-button-example btn' href='#' data-target='dropdo