Skip to content

react scripts now logs long useless logs, add option to remove them #11945

Open
ayishagisel/create-react-app
#119
@alondon17

Description

@alondon17

Is your proposal related to a problem?

After upgrading to react scripts 5, npm start now has these ugly logs each time

assets by status 3.38 KiB [cached] 1 asset
assets by chunk 8.92 MiB (name: main)
asset static/js/bundle.js 8.91 MiB [emitted] (name: main) 1 related asset
asset main.61ec10f63a1c61f3f0e3.hot-update.js 10.2 KiB [emitted] [immutable] [hmr] (name: main) 1 related asset
assets by path *.json 431 bytes
asset asset-manifest.json 403 bytes [emitted]
asset main.61ec10f63a1c61f3f0e3.hot-update.json 28 bytes [emitted] [immutable] [hmr]
asset index.html 1.69 KiB [emitted]
Entrypoint main 8.92 MiB (8.64 MiB) = static/js/bundle.js 8.91 MiB main.61ec10f63a1c61f3f0e3.hot-update.js 10.2 KiB 3 auxiliary assets
cached modules 8.43 MiB [cached] 1092 modules
runtime modules 28.3 KiB 14 modules

they weren't in the previous version and i don't care about webpack or babel,

also when an error pops i get this

ERROR in ./src/Components/HomePage/HomePage.js 7:0-51
Module not found: Error: Can't resolve './HomeasdsadPage.module.scss' in 'C:\Users...................-frontend\src\Components\HomePage'
resolve './HomeasdsadPage.module.scss' in 'C:\Users............-frontend\src\Components\HomePage'
using description file: C:\Users.................-frontend\package.json (relative path: ./src/Components/HomePage)
Field 'browser' doesn't contain a valid alias configuration
using description file: C:\Users........-frontend\package.json (relative path: ./src/Components/HomePage/HomeasdsadPage.module.scss)
no extension
Field 'browser' doesn't contain a valid alias configuration
C:\Users........-frontend\src\Components\HomePage\HomeasdsadPage.module.scss doesn't exist
.web.mjs
Field 'browser' doesn't contain a valid alias configuration
C:\Users........-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.web.mjs doesn't exist
.mjs
Field 'browser' doesn't contain a valid alias configuration
C:\Users..........-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.mjs doesn't exist
.web.js
Field 'browser' doesn't contain a valid alias configuration
C:\Users............-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.web.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
C:\Users......-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.js doesn't exist
.web.ts
Field 'browser' doesn't contain a valid alias configuration
C:\Users........-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.web.ts doesn't exist
.ts
Field 'browser' doesn't contain a valid alias configuration
C:\Users..........-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.ts doesn't exist
.web.tsx
Field 'browser' doesn't contain a valid alias configuration
C:\Users.......-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.web.tsx doesn't exist
.tsx
Field 'browser' doesn't contain a valid alias configuration
C:\Users.................-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.tsx doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
C:\Users.............-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.json doesn't exist .web.jsx
Field 'browser' doesn't contain a valid alias configuration
C:\Users.........-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.web.jsx doesn't exist
.jsx
Field 'browser' doesn't contain a valid alias configuration
C:\Users.............-frontend\src\Components\HomePage\HomeasdsadPage.module.scss.jsx doesn't exist
as directory
C:\Users..........-frontend\src\Components\HomePage\HomeasdsadPage.module.scss doesn't exist
@ ./src/App.js 12:0-58 24:21-29
@ ./src/index.tsx 10:0-24 27:37-40

when i used to get only the first two lines and that was all i needed
why was it even changed??

Describe the solution you'd like

either don't make them the default, orr add an option to hide them with a paremeter to npm start because they are useless to our team for everyday use

Describe alternatives you've considered

(Write your answer here.)

Additional context

(Write your answer here.)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions