react-scripts

npm start fails with unexpected token in file from local dependency

三世轮回 提交于 2021-02-11 08:58:23
问题 I made first-app with create-react-app where a component makes use of some material-ui components, and it is working fine when started with npm start . From this application I extracted that nice-component component in a new nice-component folder, with its package.json , the component is in a .js file that export default the component class - in Visual Studio Code I can succesfully navigate to its sources, so I would guess the setup / folder configuration is correct. In final-app application,

How does react-create-app/react-scripts find the entry point?

荒凉一梦 提交于 2021-01-18 05:30:24
问题 In this tutorial, how does npm start find the src/index/js to star the render? I can't find the configuration of this anywhere. 回答1: you can run npm run eject so that the project turn back to a normal webpack project. then you can find the configs. 回答2: while running npm run eject, you can find a config folder with all configuration files. Inside path.js file you can find the default path and if want you can change the default path there. Be careful while doing this since it is an

How does react-create-app/react-scripts find the entry point?

本小妞迷上赌 提交于 2021-01-18 05:30:06
问题 In this tutorial, how does npm start find the src/index/js to star the render? I can't find the configuration of this anywhere. 回答1: you can run npm run eject so that the project turn back to a normal webpack project. then you can find the configs. 回答2: while running npm run eject, you can find a config folder with all configuration files. Inside path.js file you can find the default path and if want you can change the default path there. Be careful while doing this since it is an

Material-UI Rendering Bugs in production / build

夙愿已清 提交于 2020-11-28 08:09:44
问题 I have big problems building my react-app. I am using material-ui/core v.4.10.2 on the normal react-scripts start dev-server everything works perfectly. But when built and served through Nginx or npm-module serve the rendering is not working correctly... (I saw similar issues on the material-ui Github, but they were all (falsely) closed Here is my package.json in case something's wrong with my dependencies (what I certainly don't think is the case) { "name": "web_app", "version": "0.0.1",

Material-UI Rendering Bugs in production / build

。_饼干妹妹 提交于 2020-11-28 08:06:57
问题 I have big problems building my react-app. I am using material-ui/core v.4.10.2 on the normal react-scripts start dev-server everything works perfectly. But when built and served through Nginx or npm-module serve the rendering is not working correctly... (I saw similar issues on the material-ui Github, but they were all (falsely) closed Here is my package.json in case something's wrong with my dependencies (what I certainly don't think is the case) { "name": "web_app", "version": "0.0.1",

Material-UI Rendering Bugs in production / build

吃可爱长大的小学妹 提交于 2020-11-28 08:04:28
问题 I have big problems building my react-app. I am using material-ui/core v.4.10.2 on the normal react-scripts start dev-server everything works perfectly. But when built and served through Nginx or npm-module serve the rendering is not working correctly... (I saw similar issues on the material-ui Github, but they were all (falsely) closed Here is my package.json in case something's wrong with my dependencies (what I certainly don't think is the case) { "name": "web_app", "version": "0.0.1",

How can I make `react-scripts build` quiet?

自作多情 提交于 2020-08-27 08:59:12
问题 I am working with a repo with a number of Node packages created with create-react-app , all of which are built and tested by the CI system. Each package's build/test, done with react-scripts build followed by react-scripts test --silent , is currently producing over twenty lines of output resulting in a build log with well over a hundred lines of material such as "File sizes after gzip" and "Find out more about deployment here." This makes it more difficult to see error messages, warnings or