Is there an overview, how the config object for the constructors of the neural network are defined?

This would be interesting:

• Has brain.NeuralNetwork and brain.recurrent.RNN the same config attributes?
• What is the description of the inputSize attribute?

Thank you for the great work with this library, it is realy amazing!

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

The current engine only exposes WebVTT subtitles as kind: 'subtitles'. When the playlist entry contains CHARACTERISTICS="public.accessibility.transcribes-spoken-dialog,public.accessibility.describes-music-and-sound", it should have kind: 'captions'. This would match how it is exposed in the Safari HLS player.

**Describe

Currently, every track added to downloads immediately starts downloading. Downloads are therefore behaving inconsistently, are not saved over program restarts, and can fail randomly without properly notifying the user. The following improvements are proposed:

• Store the list of downloads in db/on disk somewhere. The main process will manage this list.
• Allow the renderer process to query the

There used to be only one type of operational error from node-fetch: FetchError.

This is no longer the case as I can count at least six: Error, NodeError, TypeError, SyntaxError, AbortError and FetchError. All of them can be triggered in one way or another through invalid response.

We would like to unify them in some ways but it's (a) a breaking change, (b) sometimes not standa

Adding information on how to test Kefir Observables would be a nice addition to the docs. Wondering if we should put all of that into the main docs site, or have a separate site for testing with chai-kefir, or maybe moving all the docs into a kefirjs.github.io repo & website. Thoughts?

Based on FormData we shouldn't expose functions throw the prototype, for example, https://github.com/form-data/form-data/blob/b16916a568a0d06f3f8a16c31f9a8b89b7844094/lib/form_data.js#L81

We should probably use closures to keep the current this scope or change the scope of the function when you execute it.

This will keep the FormData prototype cleaner and avoid future issues when people sh

I got this error - TypeError: (("document.querySelector("#react-view").setAttribute("data-react-checksum", "" + (intermediate value)) + "")") is not a function

How can I fix it?

It'll be great to know what were the breaking changes between majors (is it safe to upgrade my projects or not) ?

Currently this information is only expressed in code changes, which is not very convienient

See https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md#900

react-i18next

https://github.com/i18next/react-i18next/blob/v9.0.0/src/Trans.js#L144-L145

const defaultValue = 
    defaults || nodesToString('', children, 0) || reactI18nextOptions.transEmptyNodeValue;

i18next-scanner

https://github.com/i18next/i18next-scanner/blob/v2.9.1/src/parser.js#L5

PS D:\React\react-native-example> expo start
Starting project at D:\React\react-native-example
Expo DevTools is running at http://localhost:19002
Opening DevTools in the browser... (press shift-d to disable)
(node:77844) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
error Invalid regular expression: /(.\fixtures\.|node_modules[\]react[\]dist[\].*