Hey guys, is there a way to âincrementallyâ production-build the vite project and skip the asset compression (and possibly other steps but mainly asset compression)?
Hi krizzl0r,
By design the full production build in Vite (and thus in our Needle Engine projects) runs all asset optimizationsâcompression, texture conversions, etc.âto keep your final website as optimized as possible. There isnât an outâofâtheâbox âincrementalâ production build mode that skips these steps. However, if youâre looking for a faster build cycle in development and want to skip asset compression (or other compression steps), you have a couple of options:
âą In your vite.config.js file you can conditionally disable the compression plugin (typically provided by viteâpluginâcompression). For example, you could remove or comment out the plugin line so it wonât run during your build:
js
import { defineConfig } from âviteâ;
import react from â@vitejs/plugin-reactâ;
import basicSsl from â@vitejs/plugin-basic-sslâ;
// import viteCompression from âvite-plugin-compressionâ; // disable asset compression
export default defineConfig({
plugins: [
react(),
basicSsl(),
// Remove or conditionally include: viteCompression({ deleteOriginFile: true })
],
build: {
// Your build options
}
});
This way, when you run âvite buildâ the asset compression step will be skipped.
âą Alternatively, if youâre using the Needle Engine export process (for example via Unity), note that the development build option already omits certain compression steps like KTX2 and Draco compression as described in our deployment docs. This can act as a kind of âincrementalâ build thatâs faster but not as optimized for final deployment.
Keep in mind that skipping these steps means the built files might be larger and load slower in the final deployment. If your main concern is build speed while iterating, using a development build or temporarily disabling the compression plugin is a common workaround.
Hope that helps! Let me know if you have any further questions.
1 replies left - Become PRO for more replies.
thread_XB9pztCZjkDsYvyL4XJw36I8
Reply to this post directly if you need further help (bottom right button)
Could you tell us a bit more about what issue youâre trying to work around? Compression is already designed to be incremental â already compressed assets will not be recompressed, and compressed data is loaded from a cache.
Iâm trying to get faster builds for quick iterations (currently hunting a non-needle related bug) where I know I did not touch any assets. Youâre right of course in that everything is cached but checking the cache still takes about ~40% of my build time.
For local development or deployment?
For local development and preview in your localhost server: turn off AutoCompress in the Needel Engine component