npm-package

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

Uploading an image with uploadcare doesn't allow me to set a cdnBase or cdnURL or something similar for custom URLs. When I upload an image it is forcing the company's cdn instead.

Describe the solution you'd like

The settings in config.json should be something like:

  media_library: {
    name: 'uploadcare

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')) {

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

Please describe what the rule should do:
In a prop definition with multiple allowed types, the rule suggests to put Boolean first to allow shorthand boolean props (see #775, #1781, #1796).

What category should the rule belong to?
[ ] Enforces code style (layout)
[x] Warns about a potential error (problem)
[ ] Suggests an alternate way of doing something (suggestion)
[ ] Other (pl

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

I've been searching around the doc and even digging in the source files, there is practically no info on how to use the message timestamp field with a producer.

The doc says we can use it :

But that's it. No examples, no details, not

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