the solution given in the guide here https://www.freecodecamp.org/forum/t/freecodecamp-challenge-guide-cash-register/16012
fails in a situation like

const cid = [["PENNY",1], ["NICKEL", 0], ["DIME", 0], ["QUARTER", 1], ["ONE", 1], ["FIVE", 5], ["TEN", 10], ["TWENTY", 20], ["ONE HUNDRED", 0]];
checkCashRegister(3, 3.01, cid);

the change due is calculated as 3.01-3, which results in

Version

2.6.10

Reproduction link

https://github.com/vuejs/vue

Steps to reproduce

1. compare the AsyncComponentFactory definition with the document

What is expected?

attribute 'componen

Do you want to request a feature or report a bug?
bug
What is the current behavior?
In current behaviour, I can create a functional component that starts with lowercase and I can use it by importing it with the uppercase name. But if I s

As we’re using the same navbar across all our projects now—docs, icons, and blog—I’m wondering if we should be linking to our GitHub org profile instead of the Bootstrap (or Icons) projects in the main navbar.

Thoughts @XhmikosR, @MartijnCuppens, @ysds, @Johann-S?

In What about &&? section we have the following code.

function foo() {
    console.log( a );
}

var a = 42;

a && foo(); // 42

result in comment should indicate that foo was called. but in fact we would get same result of "42" if first operand had been called (like in || operator). i think results of a and foo() should be different to make the example be clearer.

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 in main readme around performing multiple concurrent requests

Suggested Improvement
There is a request to remove axios.all and axios.spread (axios/axios#1042)

Although the functionality has not yet been removed, we can at least stop advertising it if there is intent (with good reason) to remove it. We can still keep

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/dc1047df725117c411959692a1ab538f65342b2e/src/algorithms/math/fibonacci/fibonacci.js#L13

This condition is redundant, the while condition covers the case where n equals 1.

p.s- I will exploit this opportunity to say thank you for this repository.

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 );

📚 Docs or angular.io bug report

Description

The examples used in the cli-builder guide have no tests ensuring they are valid. Work can start after the PR angular/angular#34362 has been merged.

What's the affected URL?**

https://angular.io/guide/cli-builder

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

https://codesandbox.io/s/vibrant-water-pepu1

Hello!

According to the documentation the verbose preset should "Output everything" in stats.json file. However, in the source code the modules property is set to false for the verbose preset. Therefore, it's not outputting "everything".

I've lost a whole da

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

I want to use Chart.js in IE9 but now it only supports IE 11+.

I remembered that the old versions (i.e. 2.5.0) supports IE 9+, but the links always pointed to the latest documentation. So where can I find documentation for historical versions?

I searched the issues but did not get an answer. Thanks.

Describe the bug
Story book is trying to add click listeners to all elements inside a panel addon. This throws console warnings when the element is an iframe

backend.js:6 Adding a click listener to iframe failed: DOMException: Blocked a frame with origin "http://localhost:9009" from accessing a cross-origin frame.

To Reproduce
Steps to reproduce the behavior:

1. I followed th

Existing Component

是

Component Name

table

Description

when i call toggleAllSelection function , the select-all were emited。but the document describe select-all will be emited when user click the button。I think the md document should describe the feature correctly

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

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