diff --git a/NPX React App Run .txt b/NPX React App Run .txt
new file mode 100644
index 00000000000..04b1b168e71
--- /dev/null
+++ b/NPX React App Run .txt
@@ -0,0 +1,6 @@
+To fix the issue, run these commands in sequence
+
+npm init
+npm install create-react-app
+npx create-react-app myapp
+
diff --git a/RunReactApp.txt b/RunReactApp.txt
new file mode 100644
index 00000000000..8001c764193
--- /dev/null
+++ b/RunReactApp.txt
@@ -0,0 +1,7 @@
+In my case, "create-react-app" was not installed. to install run this command
+
+ npm install -g create-react-app
+Once installation successful, try running
+
+npx create-react-app hello-world
+If this works for you. Great else comment what worked for you,
\ No newline at end of file
diff --git a/npx create-react-app.jsx b/npx create-react-app.jsx
new file mode 100644
index 00000000000..1c420039891
--- /dev/null
+++ b/npx create-react-app.jsx
@@ -0,0 +1,3 @@
+// npm init
+// npm install create-react-app
+// npx create-react-app myapp
\ No newline at end of file
diff --git a/solve load js wasm files.js b/solve load js wasm files.js
new file mode 100644
index 00000000000..fb9a7c66e03
--- /dev/null
+++ b/solve load js wasm files.js
@@ -0,0 +1,27 @@
+// I finally found what is the right way to load a wasm application in a wasm-bindgen project!
+
+// In fact, everything was on this page
+
+// When you compile the project without wanting to run it with a bundler, you have to run wasm-pack build with a --target flag.
+
+wasm-pack build --release --target web
+
+// This creates a .js file (pkg/test_wasm.js in my example) with everything you need to load the wasm-application.
+
+// And then this is how you use the functions created by wasm-bindgen (index.js):
+
+import init from './pkg/test_wasm.js';
+import {ex_function, ex_Struct ...} from '../pkg/test_wasm.js';
+
+function run {
+ // use the function ex_function1 here
+
+}
+
+init().then(run)
+
+// You include your index.js in your HTML file
+
+
+
+// and than it's work
\ No newline at end of file
diff --git a/solve npm start.jsx b/solve npm start.jsx
new file mode 100644
index 00000000000..cd52e176f24
--- /dev/null
+++ b/solve npm start.jsx
@@ -0,0 +1,15 @@
+// If you see this:
+
+npm ERR! UpScore@0.6.0 start: `react-scripts start`
+npm ERR! spawn ENOENT
+
+// It just means something went wrong when dependencies were installed the first time.
+
+// I suggest doing these three steps:
+
+
+npm install -g npm@latest to update npm because it is sometimes buggy.
+rm -rf node_modules to remove the existing modules.
+npm install to re-install the project dependencies.
+
+// This should fix the problem.
\ No newline at end of file
diff --git a/solve yarn build fresh react ts app.jsx b/solve yarn build fresh react ts app.jsx
new file mode 100644
index 00000000000..676cb35ac4f
--- /dev/null
+++ b/solve yarn build fresh react ts app.jsx
@@ -0,0 +1,15 @@
+// Here's how I solved this temporarily until react-scripts@4.01 is released.
+
+// 1.Place a file in your package root called verifyTypeScriptSetup.js that contains the following
+
+"use strict";
+function verifyTypeScriptSetup() {}
+module.exports = verifyTypeScriptSetup;
+
+// 2. Add the following prestart to your scripts in package.json
+
+"prestart": "cp verifyTypeScriptSetup.js node_modules/react-scripts/scripts/utils",
+
+// Now when you run npm start the errant verifyTypeScriptSetup.js in node_modules is patched.
+
+// Note: This bypasses all of CRA's checking for a valid tsconfig.json, so you better know what you're doing. Also, be sure to remove this line AFTER you migrate to react-scripts@4.01.
diff --git a/solveCSS not being supported.css b/solveCSS not being supported.css
new file mode 100644
index 00000000000..06417e393ac
--- /dev/null
+++ b/solveCSS not being supported.css
@@ -0,0 +1,113 @@
+/* All browsers behave differently and have their own type of CSS. In the case of Chrome browsers, devs need to set the WebKit pixel ratio. The code below demonstrates how to do so with various Chrome versions. */
+
+/* Chrome version 29 and above */
+@media screen and (-webkit-min-device-pixel-ratio:0)
+and (min-resolution:.001dpcm) {
+selector{ property:value; }
+}
+
+/* Test website on real Chrome version 29 and above */
+
+
+/* Chrome version 22-28 */
+@media screen and(-webkit-min-device-pixel-ratio:0) {
+ selector { -chrome-:only (;
+ property:value;
+ );}
+ }
+
+ /* Chrome, Safari, and also the Edge Browser and Firefox */
+ @media and (-webkit-min-device-pixel-ratio:0) {
+ selector { property:value; }
+ }
+
+ /* In the case of IE browsers, use conditional statements for CSS code. The example here uses the if conditional for all sections, like the header section, HTML elements, etc.*/
+
+
+
+/* Using conditional comments with head section CSS */
+
+
+/* Using conditional comments with HTML elements */
+
+
+/* IE10+ */
+@media screen and (-ms-high-contrast: active), (-ms-high-contrast: none) {
+selector { property:value; }
+}
+
+/* IE6,7,9,10 */
+@media screen and (min-width: 640px), screen\9 {
+selector { property:value; }
+}
+
+/* IE6,7 */
+@media screen\9 {
+selector { property:value; }
+}
+
+/* IE8 */
+@media \0screen {
+selector { property:value; }
+}
+
+/* IE9,10 */
+@media screen and (min-width:0\0){
+selector { property:value; }
+}
+
+/* When it comes to the Microsoft Edge browser, the process is simple as it involves a simple selector that has a property value. It also provides automatic alignment which is considered the easy way to create browser-specific CSS code.*/
+
+@supports (-ms-ime-align:auto) {
+ selector {
+ property: value;
+ }
+ }
+
+ /* In Firefox, first use the prefix for the URL. Or, use moz-appearance to show an element using platform-native styling based on the operating system’s theme.*/
+
+ @-moz-document url-prefix() {
+ selector {
+ property:value;
+ }
+ }
+
+ /* or */
+
+ @supports (-moz-appearance:none) {
+ selector { property:value; }
+ }
+
+ /* In the case of Safari web browsers, the media uses minimum resolution and WebKit appearance properties in the recent versions. In the previous Safari versions, it used pixel ratio for a CSS property*/
+
+ /* Safari 11+ */
+@media not all and (min-resolution:.001dpcm)
+{ @supports (-webkit-appearance:none) and (stroke-color:transparent) {
+selector {
+property:value;
+}
+}}
+/* Test website on real Safari 11+ */
+
+/* Safari 10.1 */
+@media not all and (min-resolution:.001dpcm){
+@supports (-webkit-appearance:none) and (not (stroke-color:transparent)) {
+selector {
+property:value;
+}
+}}
+
+/* Safari 6.1-10.0 (but not 10.1) */
+@media screen and (min-color-index:0) and(-webkit-min-device-pixel-ratio:0){
+@media {
+selector {
+property:value;
+}
+}}
+
diff --git a/solveHTML webpack plugin.txt b/solveHTML webpack plugin.txt
new file mode 100644
index 00000000000..590d4f8402d
--- /dev/null
+++ b/solveHTML webpack plugin.txt
@@ -0,0 +1,32 @@
+// The problem is indeed the file-loader, because it simply copies the file over. By the time html-webpack-plugin tries to write index.html it has already been written by file-loader, hence resulting in a conflict.
+
+// There are several ways to resolve that issue, depending on what your needs are.
+
+// You could use html-loader for your HTML, although if you expect your imported HTML to simply be copied, it isn't the correct choice. To be clear, by the imported HTML I don't mean the template used by the html-webpack-plugin.
+
+// If you want to keep using the file-loader for your other HTML files, you can exclude the index.html so html-webpack-plugin falls back to its default loader. require.resolve works like require but gives you the full path of the module instead of its content.
+
+
+{
+ test: /\.html$/,
+ exclude: [/node_modules/, require.resolve('./index.html')],
+ use: {
+ loader: 'file-loader',
+ query: {
+ name: '[name].[ext]'
+ },
+ },
+},
+
+// When no loader matches the template, the html-webpack-plugin uses an ejs loader as a fallback. If you don't need any loader for .html files, you could remove the rule entirely and it would work just fine. That is rather unlikely, otherwise you wouldn't have a .html rule in the first place, but this also means you can use the .ejs extension to not apply the .html rule, as all HTML is valid EJS. You would rename index.html to index.ejs and change your plugin configuration accordingly:
+
+new HtmlWebpackPlugin({
+ template: 'index.ejs',
+ minify: {
+ removeComments: true,
+ collapseWhitespace: true,
+ removeAttributeQuotes: true
+ },
+ chunksSortMode: 'dependency'
+})
+
diff --git a/solveImprove build process.txt b/solveImprove build process.txt
new file mode 100644
index 00000000000..9acf37e71d3
--- /dev/null
+++ b/solveImprove build process.txt
@@ -0,0 +1,24 @@
+// actually establishing a build process when there isn't much of one in place to begin with.
+
+Currently, that's pretty much the situation my group faces. We do web-app development primarily (but no desktop development at this time). Software deployments are ugly and unwieldy even with our modest apps, and we've had far too many issues crop up in the two years I have been a part of this team (and company). It's past time to do something about that, and the upshot is that we'll be able to kill two Joel Test birds with one stone (daily builds and one-step builds, neither of which exists in any form whatsoever).
+
+What I'm after here is some general insight on the kinds of things I need to be doing or thinking about, from people who have been in software development for longer than I have and also have bigger brains. I'm confident that will be most of the people currently posting in the beta.
+
+Relevant Tools: Visual Build Source Safe 6.0 (I know, but I can't do anything about whether or not we use Source Safe at this time. That might be the next battle I fight.)
+
+Tentatively, I've got a Visual Build project that does this:
+
+1.Get source and place in local directory, including necessary DLLs needed for project.
+
+2.Get config files and rename as needed (we're storing them in a special sub directory that isn't part of the actual application, and they are named according to use).
+
+3.Build using Visual Studio
+
+4.Precompile using command line, copying into what will be a "build" directory
+
+5.Copy to destination.
+
+6.Get any necessary additional resources - mostly things like documents, images, and reports that are associated with the project (and put into directory from step 5). There's a lot of this stuff, and I didn't want to include it previously. However, I'm going to only copy changed items, so maybe it's irrelevant. I wasn't sure whether I really wanted to include this stuff in earlier steps.
+I still need to coax some logging out of Visual Build for all of this, but I'm not at a point where I need to do that yet.
+
+Does anyone have any advice or suggestions to make? We're not currently using a Deployment Project, I'll note. It would remove some of the steps necessary in this build I presume (like web.config swapping).
diff --git a/solveNPMStart.txt b/solveNPMStart.txt
new file mode 100644
index 00000000000..6e701935b0e
--- /dev/null
+++ b/solveNPMStart.txt
@@ -0,0 +1,17 @@
+Author of Create React App checking in.
+
+You absolutely should not be installing react-scripts globally.
+You also don't need ./node_modules/react-scripts/bin/ in package.json as this answer implies.
+
+If you see this:
+
+npm ERR! UpScore@0.6.0 start: `react-scripts start`
+npm ERR! spawn ENOENT
+It just means something went wrong when dependencies were installed the first time.
+
+I suggest doing these three steps:
+
+npm install -g npm@latest to update npm because it is sometimes buggy.
+rm -rf node_modules to remove the existing modules.
+npm install to re-install the project dependencies.
+This should fix the problem.
\ No newline at end of file
diff --git a/solveNPmRunEject.txt b/solveNPmRunEject.txt
new file mode 100644
index 00000000000..6959a61780d
--- /dev/null
+++ b/solveNPmRunEject.txt
@@ -0,0 +1,5 @@
+create-react-app encapsulates all of the npm modules it is using internally, so that your package.json will be very clean and simple without you having to worry about it.
+
+However, if you want to start doing more complex things and installing modules that may interact with modules create-react-app is using under the hood, those new modules need to know what is available and not, meaning you need to have create-react-app un-abstract them.
+
+That, in essence, is what react-scripts eject does. It will stop hiding what it's got installed under the hood and instead eject those things into your project's package.json for everyone to see
\ No newline at end of file
diff --git a/solveReactappinstall.jsx b/solveReactappinstall.jsx
new file mode 100644
index 00000000000..eba7c1bd9e9
--- /dev/null
+++ b/solveReactappinstall.jsx
@@ -0,0 +1,5 @@
+// To fix the issue, run these commands in sequence
+
+npm init
+npm install create-react-app
+npx create-react-app myapp
diff --git a/solveaddvitetemp.txt b/solveaddvitetemp.txt
new file mode 100644
index 00000000000..ece78c9510b
--- /dev/null
+++ b/solveaddvitetemp.txt
@@ -0,0 +1,11 @@
+// Create vite project
+1. Create vite project from vue-ts template npm init vite@latest vite-vue-typescript-starter -- --template vue-ts
+2. Move contents of created folder into root of repo.
+
+$ mv vite-vue-typescript-starter/* vite-vue-typescript-starter/.gitignore .
+$ rmdir vite-vue-typescript-starter
+
+3. git add .
+4. git commit -m 'npm init vite@latest . -- --template vue-ts'
+
+// Links https://vitejs.dev/guide/#scaffolding-your-first-vite-project
diff --git a/solveavoid CSS3 rgba.html b/solveavoid CSS3 rgba.html
new file mode 100644
index 00000000000..f1255d4f854
--- /dev/null
+++ b/solveavoid CSS3 rgba.html
@@ -0,0 +1,14 @@
+// Sass will preserve the format of your color... unless it is in something other than the keyword, hex, or rgba formats. If you want to absolute format, then you have to turn into string For example : - In scss variable file
+
+// $mercury-grey: #{'rgba(230, 230, 230, 1)'};
+
+Input
+
+.class {
+ color: $mercury-grey;
+}
+
+Output:-
+.class {
+ color: rgba(230, 230, 230, 1);
+}
diff --git a/solvecreactappwork.txt b/solvecreactappwork.txt
new file mode 100644
index 00000000000..89ed72a908d
--- /dev/null
+++ b/solvecreactappwork.txt
@@ -0,0 +1,7 @@
+// Try by adding path variable, here are steps:
+
+Use the global Search Charm to search "Environment Variables".
+Click "Edit environment variables for your account"
+Click "Environment Variables" in the dialog.
+In the "System Variables" box, search for Path and edit it to include C:\Program Files\nodejs (or path of node installaton). Make sure it is separated from any other paths by a ;
+Click on apply and save the settings.
diff --git a/solvecreatereact.jsx b/solvecreatereact.jsx
new file mode 100644
index 00000000000..88a98077ec5
--- /dev/null
+++ b/solvecreatereact.jsx
@@ -0,0 +1,5 @@
+//Use This
+
+npx create-react-app my-app
+cd my-app
+npm start
\ No newline at end of file
diff --git a/solvecreatereactapp.jsx b/solvecreatereactapp.jsx
new file mode 100644
index 00000000000..e27fbf77c6d
--- /dev/null
+++ b/solvecreatereactapp.jsx
@@ -0,0 +1,16 @@
+// From https://create-react-app.dev/docs/getting-started#creating-an-app
+
+npx create-react-app my-app
+
+// (npx comes with npm 5.2+ and higher)
+
+// But you used
+
+// `create-react-app my-app`
+// If you use npm 5.1 or earlier, you can't use npx. Instead, install create-react-app globally:
+
+npm install -g create-react-app
+
+// Now you can run:
+
+create-react-app my-app
\ No newline at end of file
diff --git a/solvecreatereactappsrc.jsx b/solvecreatereactappsrc.jsx
new file mode 100644
index 00000000000..801232c6100
--- /dev/null
+++ b/solvecreatereactappsrc.jsx
@@ -0,0 +1,5 @@
+// Try with these steps :
+
+npm rm -g create-react-app
+npm install -g create-react-app
+npx create-react-app my-app
\ No newline at end of file
diff --git a/solved React App Run.txt b/solved React App Run.txt
new file mode 100644
index 00000000000..fa3a6e9d672
--- /dev/null
+++ b/solved React App Run.txt
@@ -0,0 +1,22 @@
+0
+
+Did you try recovering your dependencies? run npm install
+
+and make sure from Node and npm version at least npm more than 6 and node more than 10
+
+npm -v
+node -v
+and finally, try to delete the node_modules and package-lock and do npm i again
+
+
+
+I had this issue before so I will share what my issue was:
+
+in package.json just verify the integrity of you start command. Also try npm run start (add run to it)
+
+"scripts": {
+ "start": "react-scripts start",
+ "build": "react-scripts build",
+ "test": "react-scripts test",
+ "eject": "react-scripts eject"
+}
\ No newline at end of file
diff --git a/solved React App Work.txt b/solved React App Work.txt
new file mode 100644
index 00000000000..2af7ecec68f
--- /dev/null
+++ b/solved React App Work.txt
@@ -0,0 +1,6 @@
+In my case, "create-react-app" was not installed. to install run this command
+
+ npm install -g create-react-app
+Once installation successful, try running
+
+npx create-react-app hello-world
\ No newline at end of file
diff --git a/solved react app.txt b/solved react app.txt
new file mode 100644
index 00000000000..2af7ecec68f
--- /dev/null
+++ b/solved react app.txt
@@ -0,0 +1,6 @@
+In my case, "create-react-app" was not installed. to install run this command
+
+ npm install -g create-react-app
+Once installation successful, try running
+
+npx create-react-app hello-world
\ No newline at end of file
diff --git a/solvedLernanadYARN.txt b/solvedLernanadYARN.txt
new file mode 100644
index 00000000000..d1c500b0b57
--- /dev/null
+++ b/solvedLernanadYARN.txt
@@ -0,0 +1,29 @@
+0
+
+I don't know if this is the most simple approach but I could get it working by adding Yarn workspaces.
+
+In the main packages.json I added:
+
+ "workspaces": {
+ "packages": [
+ "packages/*"
+ ],
+ "nohoist": [
+ "**mobile**",
+ "**react**",
+ "**react-native**",
+ ...
+ ]
+ },
+In Lerna.json I added:
+
+ "useWorkspaces": true,
+From the root tsconfig.json I deleted:
+
+ "baseUrl": "./",
+ "paths": {
+ "@project/common1": ["packages/common1/lib"],
+ "@project/common2": ["packages/common2/lib"],
+ "@project/mobile": ["packages/mobile/src"],
+ "@project/cloud-functions": ["packages/cloud-functions/src"],
+ }
\ No newline at end of file
diff --git a/solvedNPMReactinstall.txt b/solvedNPMReactinstall.txt
new file mode 100644
index 00000000000..628749d9166
--- /dev/null
+++ b/solvedNPMReactinstall.txt
@@ -0,0 +1,14 @@
+You absolutely should not be installing react-scripts globally.
+You also don't need ./node_modules/react-scripts/bin/ in package.json as this answer implies.
+
+If you see this:
+
+npm ERR! UpScore@0.6.0 start: `react-scripts start`
+npm ERR! spawn ENOENT
+It just means something went wrong when dependencies were installed the first time.
+
+I suggest doing these three steps:
+
+npm install -g npm@latest to update npm because it is sometimes buggy.
+rm -rf node_modules to remove the existing modules.
+npm install to re-install the project dependencies.
\ No newline at end of file
diff --git a/solvedNPMStartWorkNode.txt b/solvedNPMStartWorkNode.txt
new file mode 100644
index 00000000000..fe75ee9e483
--- /dev/null
+++ b/solvedNPMStartWorkNode.txt
@@ -0,0 +1,7 @@
+
+
+You can run any one of the below mentioned commands to start the node server for your reactJs application:
+
+ npm run-script start
+ npm run start
+ npm start
\ No newline at end of file
diff --git a/solvedNPMwork.txt b/solvedNPMwork.txt
new file mode 100644
index 00000000000..025d843a158
--- /dev/null
+++ b/solvedNPMwork.txt
@@ -0,0 +1,10 @@
+Rename/remove your package.json file.
+
+Create a new package file by running:
+
+npm init
+Option A: Copy the dependencies you need into the newly created package.json.
+
+Option B: Install the packages and use --save to add the packages to the package.json file.
+
+Run npm install to install the dependencies.
\ No newline at end of file
diff --git a/solvedReactAppWork.txt b/solvedReactAppWork.txt
new file mode 100644
index 00000000000..5aff4b5d6e9
--- /dev/null
+++ b/solvedReactAppWork.txt
@@ -0,0 +1,8 @@
+
+
+In my case, "create-react-app" was not installed. to install run this command
+
+ npm install -g create-react-app
+Once installation successful, try running
+
+npx create-react-app hello-world
\ No newline at end of file
diff --git a/solvedRunNPM.txt b/solvedRunNPM.txt
new file mode 100644
index 00000000000..07b3b5a7e29
--- /dev/null
+++ b/solvedRunNPM.txt
@@ -0,0 +1,14 @@
+You absolutely should not be installing react-scripts globally.
+You also don't need ./node_modules/react-scripts/bin/ in package.json as this answer implies.
+
+If you see this:
+
+npm ERR! UpScore@0.6.0 start: `react-scripts start`
+npm ERR! spawn ENOENT
+It just means something went wrong when dependencies were installed the first time.
+
+I suggest doing these three steps:
+
+npm install -g npm@latest to update npm because it is sometimes buggy.
+rm -rf node_modules to remove the existing modules.
+npm install to re-install the project dependencies
\ No newline at end of file
diff --git a/solvedcoveragereport.txt b/solvedcoveragereport.txt
new file mode 100644
index 00000000000..b6dce68752a
--- /dev/null
+++ b/solvedcoveragereport.txt
@@ -0,0 +1,3 @@
+The quick fix I said in my comment, using --watchAll instead, eg: react-scripts test --coverage --watchAll.
+
+Just for future reference, I think ideally we should be using --watch, which would only run on changed files, but it gave me the same trouble. I think it's related to this issue '--coverage --watch' should calculate coverage for all files at first iteration and also this issue No coverage when running in watch mode. I'm not sure why it worked for some people and not you, presumably something to do with Git and staging of files.
\ No newline at end of file
diff --git a/solveddReactapp.txt b/solveddReactapp.txt
new file mode 100644
index 00000000000..1525376b6fb
--- /dev/null
+++ b/solveddReactapp.txt
@@ -0,0 +1,5 @@
+// To fix the issue, run these commands in sequence
+
+npm init
+npm install create-react-app
+npx create-react-app myapp
\ No newline at end of file
diff --git a/solvedfacerunreact.txt b/solvedfacerunreact.txt
new file mode 100644
index 00000000000..0b2cbf767af
--- /dev/null
+++ b/solvedfacerunreact.txt
@@ -0,0 +1 @@
+Try using 
if your images are in a public folder
\ No newline at end of file
diff --git a/solvednpmstart.txt b/solvednpmstart.txt
new file mode 100644
index 00000000000..650c9c1e75b
--- /dev/null
+++ b/solvednpmstart.txt
@@ -0,0 +1,19 @@
+262
+
+Author of Create React App checking in.
+
+You absolutely should not be installing react-scripts globally.
+You also don't need ./node_modules/react-scripts/bin/ in package.json as this answer implies.
+
+If you see this:
+
+npm ERR! UpScore@0.6.0 start: `react-scripts start`
+npm ERR! spawn ENOENT
+It just means something went wrong when dependencies were installed the first time.
+
+I suggest doing these three steps:
+
+npm install -g npm@latest to update npm because it is sometimes buggy.
+rm -rf node_modules to remove the existing modules.
+npm install to re-install the project dependencies.
+This should fix the problem
\ No newline at end of file
diff --git a/solvedorder of CSS in build.txt b/solvedorder of CSS in build.txt
new file mode 100644
index 00000000000..66def75293b
--- /dev/null
+++ b/solvedorder of CSS in build.txt
@@ -0,0 +1,14 @@
+
+
+I believe there is no answer to your question. If you google for 'wrong css order' you may found github issues for webpack older than 2 years. Like that one https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/548 and there are many others.
+
+I have solved this by combining styles into one file. I use scss so did something like:
+
+// main.scss
+
+@import 'globals';
+@import 'responsive';
+
+and in js
+
+import main.scss
\ No newline at end of file
diff --git a/solvedreactapp.txt b/solvedreactapp.txt
new file mode 100644
index 00000000000..e69de29bb2d
diff --git a/solvedreactappfreez.txt b/solvedreactappfreez.txt
new file mode 100644
index 00000000000..b8bbaefbad2
--- /dev/null
+++ b/solvedreactappfreez.txt
@@ -0,0 +1,13 @@
+I had this problem, mine got stuck at
+
+Creating a new React app in C:\project
+
+Installing packages. This might take a couple of minutes.
+Installing react, react-dom, and react-scripts...
+
+[ ................] \ fetchMetadata: sill resolveWithNewModule react-is@4.0.0
+The solution for me was to ensure npm is up to date by running:
+
+npm install npm@latest -g
+
+After this, create-react-app worked correctly.
\ No newline at end of file
diff --git a/solvedremovejavascript.txt b/solvedremovejavascript.txt
new file mode 100644
index 00000000000..7a37ed114a2
--- /dev/null
+++ b/solvedremovejavascript.txt
@@ -0,0 +1,12 @@
+I don't have a typescript version but have you tried gulp-remove-code? You can surround your JavaScript with some comments to remove whatever code you want when running your production build. This is from the above linked page:
+
+var removeCode = require('gulp-remove-code');
+
+gulp.src('./src/file.js')
+ .pipe(removeCode({ production: true }))
+ .pipe(gulp.dest('./dist'))
+
+
+//removeIf(production)
+value = JSON.stringify({key: 'value'}, null, 2);
+//endRemoveIf(production)
\ No newline at end of file
diff --git a/solvedstart app using grpc web.txt b/solvedstart app using grpc web.txt
new file mode 100644
index 00000000000..b4850ce59c6
--- /dev/null
+++ b/solvedstart app using grpc web.txt
@@ -0,0 +1,20 @@
+2
+
++250
+This is most likely caused by the common CORS Browser restrictions, and not exactly by angular. This question contains great guidance on CORS.
+
+Calling HTTP services from a Node app (or from postman) will not enforce CORS, while calling it from a market standard browser certainly would.
+
+I know there is far more to it than my next simplified comments but this should give you a starting point (a deeper dive is in the links I shared above)
+
+For browsers to execute XMLHttpRequest's from one website to other domains (or other ports of the same domain):
+
+the browser will send an OPTIONS HTTP request before every real request to the other domain and only allow the actual request when the OPTIONS response headers authorize it.
+the "other" website must be configure to reply to OPTIONS requests with specific Headers (Access-Control-Allow-Origin, Access-Control-Request-* ...).
+==> If the other server does not reply to OPTIONS requests or does not provide the appropriate headers in the OPTIONS response, you can get a range of different errors, and "Response closed without headers" is one of them.
+
+I believe your gRPC web application is not configured with the proper CORS to authorize communications from the website where you are hosting your angular application (even if it is localhost, you would still need to configure it).
+
+This article has practical guidance on how to configure CORS on .netcore applications
+
+and finally, This github issue / responses contains some more info about a similar error some people faced with gRPC, you might have stepped into the same one. If you have already configured your CORS rules.
\ No newline at end of file
diff --git a/solvedstartreact.txt b/solvedstartreact.txt
new file mode 100644
index 00000000000..5eaa658b71a
--- /dev/null
+++ b/solvedstartreact.txt
@@ -0,0 +1,8 @@
+53
+
+In my case, "create-react-app" was not installed. to install run this command
+
+ npm install -g create-react-app
+Once installation successful, try running
+
+npx create-react-app hello-world
\ No newline at end of file
diff --git a/solvegetyarn.txt b/solvegetyarn.txt
new file mode 100644
index 00000000000..24eb84c3c03
--- /dev/null
+++ b/solvegetyarn.txt
@@ -0,0 +1,8 @@
+// Migrating from 4.0.2 to 4.0.3
+Inside any created project that has not been ejected, run:
+
+npm install --save --save-exact react-scripts@4.0.3
+
+or
+
+yarn add --exact react-scripts@4.0.3
\ No newline at end of file
diff --git a/solvenpm audit.txt b/solvenpm audit.txt
new file mode 100644
index 00000000000..595eeedb896
--- /dev/null
+++ b/solvenpm audit.txt
@@ -0,0 +1,12 @@
+
+Often times, this is related to package-lock.json messing. I would suggest to try to:
+
+1 - Delete your package-lock.json
+
+2 - Delete your node_modules folder
+
+3 - Try npm install again
+
+This used to fix several issues when adding new packages in my angular apps.
+
+Good luck!
\ No newline at end of file
diff --git a/solvenpxreactapp.txt b/solvenpxreactapp.txt
new file mode 100644
index 00000000000..303302db6ce
--- /dev/null
+++ b/solvenpxreactapp.txt
@@ -0,0 +1,7 @@
+// In my case, "create-react-app" was not installed. to install run this command
+
+ npm install -g create-react-app
+Once installation successful, try running
+
+npx create-react-app hello-world
+If this works for you. Great else comment what worked for you
\ No newline at end of file
diff --git a/solvereact-app fail of compile.txt b/solvereact-app fail of compile.txt
new file mode 100644
index 00000000000..b578bd5e293
--- /dev/null
+++ b/solvereact-app fail of compile.txt
@@ -0,0 +1,12 @@
+ // I have had the exact same errors when I created app using the create-react-app and setup the eslint for the application.
+
+// The eslint errors were showing up in the browser rather than in the console.
+
+// Once, I debugged all the dependencies. It seems that the react-scripts was causing the lint errors for me.
+
+// The newest version of the react-scripts:"4.0.0" may have some breaking changes which could be causing the eslint to throw the errors in the browser.
+
+Solution:
+This issue has been fixed in the react-scipts:"4.0.3" but, the eslint errors present in the project are not converted to warnings by default. You have to create an .env file which should contain a ESLINT_NO_DEV_ERRORS=true flag. Due to this flag, you will receive the eslint errors as warnings and not as errors in the development.
+
+This flag is ignored during production and when they are any git hooks running, which will in turn cause an error when you are trying to commit the code with an eslint error in it.
\ No newline at end of file
diff --git a/solvereactapp.txt b/solvereactapp.txt
new file mode 100644
index 00000000000..49af0b0a740
--- /dev/null
+++ b/solvereactapp.txt
@@ -0,0 +1,9 @@
+// In my case, "create-react-app" was not installed. to install run this command
+
+ npm install -g create-react-app
+
+Once installation successful, try running
+
+npx create-react-app hello-world
+
+If this works for you. Great else comment what worked for you
\ No newline at end of file
diff --git a/solvereactappnpm.txt b/solvereactappnpm.txt
new file mode 100644
index 00000000000..28fe9e54000
--- /dev/null
+++ b/solvereactappnpm.txt
@@ -0,0 +1 @@
+// Try deleting your node_modules directory and package-lock.json file. Then run npm install
diff --git a/solvereactappyarn.txt b/solvereactappyarn.txt
new file mode 100644
index 00000000000..f739dd22712
--- /dev/null
+++ b/solvereactappyarn.txt
@@ -0,0 +1,8 @@
+// So the first thing you should try is, well, the commands above.
+npm uninstall -g create-react-app. ...
+yarn global remove create-react-app. ...
+npm update npx. ...
+npm install npm@latest -g. ...
+npm cache clean --force. ...
+where/which create-react-app. ...
+Find Hidden Folders (Mac and Windows) ...
\ No newline at end of file
diff --git a/solvereactprojectstart.jsx b/solvereactprojectstart.jsx
new file mode 100644
index 00000000000..61e17e832c5
--- /dev/null
+++ b/solvereactprojectstart.jsx
@@ -0,0 +1,21 @@
+// Create a .env file at your project root and specify port number there PORT=3005 then in package json start script use like this "start": "react-scripts start" Sample package json file below
+
+{
+ "name": "r",
+ "version": "0.1.0",
+ "private": true,
+ "devDependencies": {
+ "react-scripts": "0.8.4"
+ },
+ "dependencies": {
+ "react": "^15.4.2",
+ "react-dom": "^15.4.2"
+ },
+ "scripts": {
+ "start": "react-scripts start",
+ "build": "react-scripts build",
+ "test": "react-scripts test --env=jsdom",
+ "eject": "react-scripts eject"
+ }
+ }
+
\ No newline at end of file
diff --git a/solverunning npm start.jsx b/solverunning npm start.jsx
new file mode 100644
index 00000000000..985a17ec793
--- /dev/null
+++ b/solverunning npm start.jsx
@@ -0,0 +1,13 @@
+// It looks like you might not have defined a start script in your package.json file or your project does not contain a server.js file.
+
+// If there is a server.js file in the root of your package, then npm will default the start command to node server.js.
+
+https://docs.npmjs.com/misc/scripts#default-values
+
+// You could either change the name of your application script to server.js or add the following to your package.json
+
+"scripts": {
+ "start": "node your-script.js"
+}
+
+Or ... you could just run node your-script.js directly
\ No newline at end of file
diff --git a/solverunreact.txt b/solverunreact.txt
new file mode 100644
index 00000000000..8d04969c89f
--- /dev/null
+++ b/solverunreact.txt
@@ -0,0 +1,3 @@
+With react, you don't have to use liveserver. Go to your terminal and then navigate to the root of your react project and then run npm start.
+
+This information is also available in the react docs and create-react-app docs
\ No newline at end of file
diff --git a/solvesemantic-ui-css to create-react-app .jsx b/solvesemantic-ui-css to create-react-app .jsx
new file mode 100644
index 00000000000..da0e5c85fd3
--- /dev/null
+++ b/solvesemantic-ui-css to create-react-app .jsx
@@ -0,0 +1,10 @@
+// The main reason for this is an extra ";" at line 19990 of semantic.css If removed, everything goes fine.
+
+@font-face {
+ font-family: 'Step';
+ src: url(data:application/x-font-ttf;charset=utf-8;;base64,AAEAAAA... // this line
+ }
+
+ // While this solution works, I would caution that Semantic-UI has been unmaintained for several years now. Fomantic-UI is the community fork that is maintained and incorporates both bug fixes and additional features like toasts.
+
+// FYI, this bug was recently discovered so it exists in the current release version of Fomantic-UI (2.8.8), but it has been fixed in the code base and tagged for the next release.
diff --git a/solveyarnstart.jsx b/solveyarnstart.jsx
new file mode 100644
index 00000000000..176ebb5d091
--- /dev/null
+++ b/solveyarnstart.jsx
@@ -0,0 +1,6 @@
+// I had this problem. I figured the best way is this.
+
+npm i -g create-react-app
+create-react-app my-react-app //or whatever you want your project to be
+cd my-react-app
+yarn start
\ No newline at end of file