We have a bunch of features we can move from the Beta section to the permanent docs.

I think everything under https://www.netlifycms.org/docs/beta-features/ except i18n and Nested collections can be moved

It would make sense to move each feature at a time to make sure we're not cluttering the docs

I've read many similar closed issues, but haven't found a good documented solution on what can I do as a consumer of ky package if I need to support e.g iOS 10.0 browser (that breaks on async/await support currently).

I agree that it's not related to ky itself, but can be a nice help for the consumers of the package.

In our particular can we don't use babel (we use typescript), so I'm

Describe the bug

It surprised me as well, but apparently NPM is case sensitive

https://www.npmjs.com/package/webStorage
https://www.npmjs.com/package/webstorage

To Reproduce

https://bundlephobia.com/result?p=webStorage

Expected behavior

I should be shown stats for webStorage package, but I see webstorage instead.

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

Please describe what the rule should do:
Since Vue v2.1.0, Vue.nextTick and vm.$nextTick return a Promise if no callback is provided. So both of the following are valid:

• Vue.nextTick(callback)
• Vue.nextTick().then() / await Vue.nextTick()

Or inside components:

• this.$nextTick(callback)

Hi, im trying to use Hashids with Typescript and Node.

import Hashids from 'hashids';

I'm not getting any Typescript errors in the editor, but Im getting this error when the code is compiled.

Using ts-node version 8.5.4, typescript version 3.7.5

`Error: No valid exports main found for 'node_modules\hashids'
at resolveExportsTarget (internal/modules/cjs/loader.js:625:9)

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

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.

Is your feature request related to a problem? Please describe.
Currently, there are many errors that do not provide certain metadata. For example, TOPIC_AUTHORIZATION_FAILED does not provide the topic(s) that failed to authorize. We provide our producer with multiple brokers and use sendBatch to send to multiple topics. It appears that some messages go through to one broker but not another bu