npm-package

Is your feature request related to a problem? Please describe.

For some reason Amazon REST api's require the content-type to be set to "application/x-amz-json-1.1" instead of the standard "application/json"

Currently the content-type header is set automatically for json data overriding any headers passed in to the request.

It would be useful to first check if the header is set before overriding it:

if (!this.request.headers.set('content-type')) {

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:

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

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

Please describe what the rule should do:
In Vue you can use test($event.detail) as well as event => test(event.detail) to achieve the same thing. 1. should be preferred.

1. test($event.detail)

<Component
  @click="test($event.detail)"
/>

2. event => test(event.detail)

<Component
  @click="event => test(event.detail)"
/>

**What category should

isValid always assumes the type of the value, because the first argument should be unknown (like it is for ow itself): https://github.com/sindresorhus/ow/blob/3728d9119a19e1a95cb58bebe602afd308c40630/source/index.ts#L39

Looking over the rest of the file, it seems this mistake was made in several places; ReusableValidator should probably also not use T for the value (and assert?)

Using the latest release 2.2.8, the typescript definition file in the package is defined like

import Hashids from '../lib/hashids'

export = Hashids

with that import to the source code. Unfortunately, this is less robust than building Typescript and including the definitions only, as the success of the build depends on the user having a compatible Typescript configuration.

Fo

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