Christophe Hurpeau

Provide an `native` export without react-native aliases for react-native-web

3

Hello, Currently, importing `styled-components/native` in a react-native-web projects does import a lot from react-native-web because there is a [`require('react-native');`](https://github.com/styled-components/styled-components/blob/main/packages/styled-components/src/native/index.ts#L12) in the dist file [for aliases](https://github.com/styled-components/styled-components/blob/main/packages/styled-components/src/native/index.ts#L20-L82) so webpack cannot tree-shake it....

Support $ReadOnlyArray

17

[](https://issuehunt.io/r/gajus/flow-runtime/issues/199) This is a: - [ ] Bug Report - [x] Feature Request - [ ] Question - [ ] Other Which concerns: - [x] flow-runtime - [ ] babel-plugin-flow-runtime...

This flag could introduce some performance enhancements

export type to be able to reuse it when typing ref

feat(noUnusedExports): make tsconfigPath optional by using typescript-eslint utils

1

Guess the option using typescript services

tests: missing loader error

2

test case for #14

Invalid infobox value for https://fr.wikipedia.org/wiki/Marseille

2

page: https://fr.wikipedia.org/wiki/Marseille Wikipedia value: `13055 et de [[Secteurs et arrondissements de Marseille|13201 à 13216]]` Expected: `13055 et de 13201 à 13216` probably ? Actual: `Secteurs et arrondissements de Marseille` ```...

Support for async handler is missing, specifically to wait for them to finish (or timeout) before exiting