React-Sight VS webpack-bundle-analyzer

React Sight marks its presence in the domain of React debugging tools by offering a unique visualization advantage. Designed to delineate the component hierarchy in React applications, this tool proves to be a reliable companion for developers. Compatible with React version 14.7 and onwards, including Fiber, React Sight extends its support to libraries like React Router and Redux.

React Sight

You're much better off looking at an actual mock-up and visually breaking things apart as the design for your components. If, after you write the code, you'd like a relationship graph of component then you can use a tool like React Sight.

React Sight used to be available but it's recently been removed from both Chrome and FF stores. You can build your own though by following the instructions in the repository README.md.

Checkout React Sight by Clicking here

Source

React Sight - Looks good, page on the Chrome Extension store no longer exists.

I have found react-monocle (https://github.com/team-gryff/react-monocle) & react-sight(https://github.com/React-Sight/React-Sight). Both seem to be deprecated. Is there a better way to do this?

9. React Sight

I used to use webpack-bundle-analyzer but we have switched the builder to browser-esbuild now.

First start by running a webpack bundle analysis to see what exactly is bundled. You might be surprised about things being included that you didn't expect which can help with where to look.

Firstly I recommend taking a look at the structure of the webpack output with something like webpack-bundle-analyzer for any obvious over bundling issues.

See: https://github.com/webpack-contrib/webpack-bundle-analyzer

Webpack Bundle Analyzer

npm run analyse - analyse bundle with webpack-bundle-analyzer

This was my question as well. The article does answer the question, but off the bat I'd assumed the author was talking about output/dist. The web treemap cli is a great tip. If you are using webpack, webpack-bundle-analyzer is a helpful tool for quickly finding bloated packages. It's definitely helped me cut down my build times: https://github.com/webpack-contrib/webpack-bundle-analyzer

Here are a few tipps where you could save some time: 1)check angular.json (configurations -> "your ci config") - look for buildOptimizer / optimization 2)If you run npm ci during your pipeline it might make sense to create the node modules folder beforehand, it seems to save time (https://github.com/npm/cli/issues/2011) 3)Use ng build --stats-json to analyze your build 4)Use https://github.com/webpack-contrib/webpack-bundle-analyzer (also works together with 3. ) 5)Check your package.json for unused dependencies 6)Check your imports, import only what is needed Hope this helps

- `npm run start` - Start the app - `npm run lint` - Lint the project - `npm run test` - Run unit tests - `npm run build` - Build the project - `npm run build:prod` - Build the project in production mode - `npm run build:prod:stats` - Build the project in product mode with stats - `npm run analyse` - Analyse bundle with [webpack-bundle-analyzer](https://github.com/webpack-contrib/webpack-bundle-analyzer) - `npm run compodoc` - Generate [compodoc](https://github.com/compodoc/compodoc) documentation - `npm run version` - Generate changelog - `npm run prettier` - Format the whole project - `npm run audit` - Audit this application using Sonatype OSS Index