to reproduce:

1. go to localhost:8000/donate locally
2. click on show other ways to donate.
3. decrease the screen size below 400px

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:

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

What is the current behavior?
Event handlers on elements are fired twice, when hovering from one element onto the next.

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and i

In the documentation for both Tooltips and Popovers is the caveat: "opt-in for performance reasons, so you must initialize them yourself." But I'm having trouble finding a detailed explanation of "performance reasons." The caveat is at least 6 years old, which makes me wonder i

The typings file specifies:

setVibrancy(type: 'appearance-based' | 'light' | 'dark' | 'titlebar' | 'selection' | 'menu' | 'popover' | 'sidebar' | 'medium-light' | 'ultra-dark'): void;

whereas docs suggest that passing null disables vibrancy.

The argument type should be nullable

In many places in the documentation (example: 'socket' event), socket is not necessarily a net.Socket, but always a stream.Duplex (which net.Socket inherits from). We should at least mention that if we don't want to replace all references.

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

https://twitter.com/rauschma/status/1181852019264503808

We should give a more helpful message when missing "lib": ["dom"].

If accessing a property on a type that was

• empty and
• declared in the global scope and
• named after a pattern that matches /^HTML\w+Element$/

it is likely a forward declaration for DOM environments, and we should provide an error message like:

Pro

📚 Docs or angular.io bug report

Description

In the Component Class section, the reference of angul

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

Is it more preferable to use @material-ui/core/styles instead of @material-ui/styles if material-ui is used?

Also according to the Minimizing Bundle Size Guide, anything below 2nd level import is considered private and can cause module duplication in your bundle. So should I import makeStyles like this to minimize bundle size?

So getAllowedLocations is mentioned in the Atom flight manual, but it's not mentioned elsewhere in the docs. I thought I could implement just getDefaultLocation without having to also implement getAllowedLocations, but I get the following in the developer tools:

`C:\Use

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

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:

• [X ] Missing or needed
• Confusing
• [X ] Not Sure?

Please Explain in Detail...

I searched the documentation and could not find if it is possible to show two graphs of different Y-Axis value types/scale on the same chart. I understand that the Y-Axis labels would probably have to be hidden, but

Hi, this is a feature request I suppose. The zip file download from the home page is a bit of a 'zip bomb'. I think it would be better to unzip into a contained folder as this can be quite annoying.

https://github.com/storybookjs/presets/blob/master/packages/preset-storysource/index.js

• Move the preset from the presets repo into this package
• Update it to use source-loader
• Update docs

Existing Component

是

Component Name

site

Description

add TOC quick access.

example:
antd
![image](https://user-images.githubusercontent.com/8358236/482508

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

It will be nice to have a document guide to migrate from v0.100.2 to v1.0. Else if it's already there can it be displayed in a more prominent place in the landing page. I had a lot of struggle in migrating my things.