rollup-plugin-visualizer
vite-tsconfig-paths
Our great sponsors
| rollup-plugin-visualizer | vite-tsconfig-paths | |
|---|---|---|
| 2 | 5 | |
| 1,731 | 1,167 | |
| - | - | |
| 7.3 | 6.5 | |
| 14 days ago | about 1 month ago | |
| TypeScript | TypeScript | |
| MIT License | MIT License |
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.
rollup-plugin-visualizer
-
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).
vite-tsconfig-paths
-
From webpack to vite: custom module resolution, sass import, babel config
Following suggestion in the issue, i looked at vite-tsconfig-paths which is even better because i already have configured vscode through typescript config:
-
Trying Vite for team's new front end project, can't seem to configure a base import path?
Try this one. https://github.com/aleclarson/vite-tsconfig-paths
-
Migrating from Create React App (CRA) to Vite
We need vite-tsconfig-paths in order to tell Vite how to resolve absolute paths from the tsconfig file. This way you can import modules like this:
-
Vite: Import path alias only setting tsconfig.json
You can use vite-tsconfig-paths on SvelteKit project. And it doesn't work, plese try delete generated folder for dev server like .svelte-kit.
-
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.
What are some alternatives?
vite - Next generation frontend tooling. It's fast!
DefinitelyTyped - The repository for high quality TypeScript type definitions.
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
tsconfig-paths-webpack-plugin - Load modules according to tsconfig paths in webpack.
vite-plugin-svgr - Vite plugin to transform SVGs into React components
Snowpack - ESM-powered frontend build tool. Instant, lightweight, unbundled development. ✌️ [Moved to: https://github.com/FredKSchott/snowpack]
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
svgr - Transform SVGs into React components 🦁