tsconfig-paths-webpack-plugin
Load modules according to tsconfig paths in webpack. (by dividab)
rollup-plugin-visualizer
📈⚖️ Visuallize your bundle (by btd)
Our great sponsors
| tsconfig-paths-webpack-plugin | rollup-plugin-visualizer | |
|---|---|---|
| 2 | 2 | |
| 586 | 1,731 | |
| 1.0% | - | |
| 4.3 | 7.3 | |
| 8 months ago | 15 days ago | |
| TypeScript | TypeScript | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tsconfig-paths-webpack-plugin
Posts with mentions or reviews of tsconfig-paths-webpack-plugin.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-20.
-
Can we override component at compile time
You can see an example of such resolver here: https://github.com/dividab/tsconfig-paths-webpack-plugin/blob/master/src/plugin.ts
-
Using Vite with React
We already have configured path aliases with webpack and tsconfig - so I wanted to keep that behavior. Luckily we have the vite-tsconfig-paths exactly for that. It worked well. I could also try using the alias for that.
rollup-plugin-visualizer
Posts with mentions or reviews of rollup-plugin-visualizer.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-20.
-
PageSpeed / Lighthouse - Reduce unused JavaScript
I think https://github.com/btd/rollup-plugin-visualizer can help with checking which packages are the largest.
-
Using Vite with React
In our "old" build system - I configured webpack-bundle-analyze to inspect bundle chunks and understand what it made of. I added rollup-bundle-visualyzer instead (although there is an issue that the reported size is not correct).
What are some alternatives?
When comparing tsconfig-paths-webpack-plugin and rollup-plugin-visualizer you can also consider the following projects:
vite-tsconfig-paths - Support for TypeScript's path mapping in Vite
vite - Next generation frontend tooling. It's fast!
svgr - Transform SVGs into React components 🦁
awesome-vite - ⚡️ A curated list of awesome things related to Vite.js
webpack-bundle-analyzer - Webpack plugin and CLI utility that represents bundle content as convenient interactive zoomable treemap
wmr - 👩🚀 The tiny all-in-one development tool for modern web apps.
vite-plugin-svgr - Vite plugin to transform SVGs into React components
nivo - nivo provides a rich set of dataviz components, built on top of the awesome d3 and React libraries
esbuild - An extremely fast bundler for the web
tsconfig-paths-webpack-plugin vs vite-tsconfig-paths
rollup-plugin-visualizer vs vite
tsconfig-paths-webpack-plugin vs svgr
rollup-plugin-visualizer vs awesome-vite
tsconfig-paths-webpack-plugin vs awesome-vite
rollup-plugin-visualizer vs webpack-bundle-analyzer
tsconfig-paths-webpack-plugin vs wmr
rollup-plugin-visualizer vs vite-plugin-svgr
tsconfig-paths-webpack-plugin vs vite-plugin-svgr
rollup-plugin-visualizer vs nivo
tsconfig-paths-webpack-plugin vs esbuild
rollup-plugin-visualizer vs svgr