npm-package

Describe the bug
I have setup i18n in a single_file, need to test some feature, but I'll need a specific setup, but I encounter an issue while testing that.
Folder collection does work very good, but when I'm trying to save a single_file, I got the following error.

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'get')

Screenshots
ht

Got has a very good coverage test-wise. Would be nice to port relevant tests that we're missing over to Ky.

Note: Not for https://github.com/sindresorhus/ky/blob/master/test/browser.js, but for everything else.

My goal is to have the best documentation for each provided type.

If something is unclear in any of the types, please comment or open a PR to improve it.

Some things you could contribute:

• Fix typos.
• Improved description of the type.
• More examples.
• Provide more real-world use-cases. This helps the user understand where a type might come in handy.
• Add links to relevant discu

Describe the bug

The "ES2015 exports introduced. Not side-effect free yet, hence limited tree-shake ability." Tooltip in the Size-per-package-Version graph is displayed behind the graphs bars, possibly making the tooltip text unreadable.

To Reproduce

Found on this page:

The goal of this project is to make itself obsolete. We should try to get browsers to fix their own styles so we don't have to work around them indefinitely.

If you want to help out:

• Pick a style in modern-normalize.css
• Go to the relevant browser issue trackers ([Chrome](http://dev.chromium.org/for-test

This is a follow-up to v2.0 #65 to switch the default parsing on supported systems so we support BigInt strings transparently.

What rule do you want to change?
vue/match-component-file-name

Does this change cause the rule to produce more or fewer warnings?
Same.

How will the change be implemented? (New option, new default behavior, etc.)?
New suggestions

I use Array<Uint8Array> as a value. But The uint8Array is treated as string.

function arrayString(val) {
  var result = '{'
  for (var i = 0; i < val.length; i++) {
    if (i > 0) {
      result = result + ','
    }
    if (val[i] === null || typeof val[i] === 'undefined') {
      result = result + 'NULL'
    } else if (Array.isArray(val[i])) {
      result = result + arrayStr

For popular things that makes sense. Suggestions welcome, but I'm not going to add more than maybe 30. So make it worth it.

Don't do a PR. I'll add them all at once when we've decided on what to include.

Currently, InfiniteScroll adds the scroll listeners only when mounting. That means that if the scroll target (whether it's specified or default to window) changes, the component won't request a new page load if there's some scroll in the new target.

I guess the solution is to check in componentWillReceiveProps if there's some change in target, and if it's the case, remove the current lis