Publishing Reusable Components with Vite Library Mode
Vite Library Mode switches your build from an app bundle to a distributable package. Learn how to configure build.lib, manage peer dependencies, and verify the output.
Loading…
ReadMeFeed / Community knowledge
#frontend-build
Real questions. Useful conversations. Find the people who know your stack.
Using Vite’s VITE_ Prefixed Environment Variables in Client Code
Learn how Vite exposes only VITE_ prefixed environment variables to client code via import.meta.env, with a worked example, limits, and common pitfalls.
Less Mixins: Default Parameters or Guards for Optional Styles
Default parameters cover most Less mixin needs; guards earn their keep for type checks and feature flags. A comparison table, a button example, and how to verify the compiled CSS.
lessVite production build asset 404s when deploying to subpaths
Asset Resolution Divergence Vite's development server handles asset resolution from memory using root-relative paths. However, the production build process uses Rollup to rewrite asset URLs based on the base configuration in vite.config.js . This creates a discrepancy when an application is hosted under a subpath (e.g., /my-app/ ) or a CDN prefix rather than
vite
rollupSass Variable Override Limitations in Production Build Pipelines
Customization via Sass Variables Bulma relies on a Sass-based architecture where user-defined variables must be declared before the core framework import so overrides take effect. This customization happens at compile time, so redefining the primary color palette or spacing scale requires a rebuild rather than a runtime change. Production Build Constraints W
sass