Add // tslint:disable-next-line:no-console in the line right before your calls to console.log to prevent the error message only once. If you want to disable the rule entirely add the following to your tslint.json (most likely in your root folder): { “rules”: { “no-console”: false } }
This worked for me: npx create-react-app@latest your-project-name –use-npm
Unfortunately, keeping any key in your React client, even if you are using gitignore and an .env file, is not secure. As pointed out by @ClaudiuCreanga, React environment variables are embedded in the build and are publicly accessible. You should really only save API keys or secrets in your backend such as Node / Express. … Read more
Solving this without importing and exposing package.json to the create-react-app Requires: version 1.1.0+ of create-react-app .env REACT_APP_VERSION=$npm_package_version REACT_APP_NAME=$npm_package_name index.js console.log(`${process.env.REACT_APP_NAME} ${process.env.REACT_APP_VERSION}`) Note: the version (and many other npm config params) can be accessed Note 2: changes to the .env file will be picked only after you restart the development server
I was struggling with the same problem and actually it turns out that a simple change seems to do the trick. I just updated the moduleDirectories field in jest.config.js. Before moduleDirectories: [‘node_modules’] After moduleDirectories: [‘node_modules’, ‘src’] Hope it helps.
You can create a new React app in the current directory by writing . instead of a project name. create-react-app .
To fix this issue simply upgrade react-scripts package (check latest version with npm info react-scripts version): Replace in your package.json “react-scripts”: “^3.x.x” with “react-scripts”: “^3.4.1” (or the latest available version) (optional for some) Delete your node_modules folder Run npm install or yarn install Some people reported that this issue was caused by running npm audit … Read more
The error is telling you that you are importing incorrectly. Here’s the code you have to add: import { Home } from ‘./layouts/Home’; This is incorrect because you’re exporting as the default export, not as a named export. Check this line: export default Home; You’re exporting as default, not as a name. Thus, import Home … Read more
It’s a Web App Manifest that describes your application and it’s used by e.g. mobile phones if a shortcut is added to the homescreen. From MDN (linked above): The web app manifest provides information about an application (such as name, author, icon, and description) in a JSON text file. The purpose of the manifest is … Read more
Edit: as noted by Meng-Yuan Huang, this issue no longer occurs in react-scripts@^4.0.1 This error occurs because react-scripts has a direct dependency on the 2.xx range of @typescript-eslint/parser and @typescript-eslint/eslint-plugin. You can fix this by adding a resolutions field to your package.json as follows: “resolutions”: { “**/@typescript-eslint/eslint-plugin”: “^4.1.1”, “**/@typescript-eslint/parser”: “^4.1.1” } NPM users: add the … Read more