It seems to be correct behaviour in create-react-app according to Issue #1632. Gaeron: This is expected. You can delete .map files from the build output if you want to disable it, although you’ll get console warnings about them missing. There is no harm in leaving them in though in my opinion. Client code is already … Read more
You probably need to copy the objects: export const initSelect = (data) => { return data.map((item) => ({ …item, selected: false })); }
You should have a <BrowserRouter> (or any of the provided routers) higher up in the tree. The reason for this is that the <BrowserRouter> provides a history context which is needed at the time the routes are created using useRoutes(). Note that higher up means that it can’t be in the <App> itself, but at … Read more
There have been some recent developments and with a new version of Typescript (eg. 3.0.1) and styled-components (eg. 3.4.5) there’s no need for a separate helper. You can specify the interface/type of your props to styled-components directly. interface Props { onPress: any; src: any; width: string; height: string; } const Icon = styled.Image<Props>` width: ${p … Read more
By default mapDispatchToProps is just dispatch => ({ dispatch }). So if you don’t specify the second argument to connect(), you’ll get dispatch injected as a prop in your component. If you pass a custom function to mapDispatchToProps, you can do anything with the function. A few examples: // inject onClick function mapDispatchToProps(dispatch) { return … Read more
You can add the plugins as suggested by @Vikramaditya. Then to generate the production build. You have to run the the command NODE_ENV=production webpack –config ./webpack.production.config.js If using babel, you will also need to prefix BABEL_ENV=node to the above command.
You’re using a combination of Babel 6 and Babel 7. There is no guarantee of compatibility across versions: “@babel/core”: “^7.0.0-beta.40”, “babel-cli”: “^6.26.0”, “babel-loader”: “^8.0.0-beta.0”, “babel-plugin-lodash”: “^3.3.2”, “babel-plugin-react-transform”: “^3.0.0”, “babel-preset-react”: “^6.24.1”, should be “@babel/core”: “^7.0.0-beta.40”, “@babel/cli”: “^7.0.0-beta.40”, “babel-loader”: “^8.0.0-beta.0”, “babel-plugin-lodash”: “^3.3.2”, “babel-plugin-react-transform”: “^3.0.0”, “@babel/preset-react”: “^7.0.0-beta.40”, and query: { presets: [‘react’, ‘es2015’], plugins: [‘transform-class-properties’] } would be … Read more
So after reading through some related answers (specifically this one and this one and looking at @basarat’s answer to the question, I managed to find something that works for me. It looks (to my relatively new React eyes) like Connect was not supplying an explicit interface to the container component, so it was confused by … Read more
Even React docs mention the custom ref prop as a more flexible approach to forwardRef: If you use React 16.2 or lower, or if you need more flexibility than provided by ref forwarding, you can use this alternative approach and explicitly pass a ref as a differently named prop. There is also a gist, in … Read more
“alignSelf” does the same as ‘display: inline-block’ would in common HTML/CSS and it works very well for me. <View style={{backgroundColor: ‘#000000’, alignSelf: ‘flex-start’ }}> <Text style={{color: ‘#ffffff’}}> Sample text here </Text> </View>