Compressing lines in strings

[danrossi]

I require some further information regarding lines in strings. Vite has migrated to oxc as the minifier. However after many hours trying to figure out what is going on as the strings are compressed without minify enabled as I format them in a plugin first. Oxc does not compress lines in strings it undoes the transformation in a plugin so it reverses the transformation back to lines. Terser does so it's a breaking change to previous minifiers.

A string like

export const FRAGMENT_TRANSFORM2 = `TEST \n TEST \n TEST \n TEST`;

Is reversed back to

`,FRAGMENT_TRANSFORM2=`TEST 
 TEST 
 TEST 
 TEST
`;e

In Terser it's

var T="TEST\nTEST\nTEST\nTEST",E="TEST \n TEST \n TEST \n TEST",S="TEST \n TEST \n TEST \n TEST";export{T as FRAGMENT_TRANSFORM,E as FRAGMENT_TRANSFORM2,S as FRAGMENT_TRANSFORM3};

Is there a known work around before forcing terser as the minifier to compress a module full of very large GLSL shader strings with lines in it ? Terser has the same speed as Oxc so not sure why they migrated to it so early so migrating to it is a breaking change. .

The documentation here provides no resolution and no reason to why it's not compressing strings or an option to. It's very strange documentation and seems unfinished.

https://oxc.rs/docs/guide/usage/minifier/faq.html#new-lines-in-strings-are-not-removed

Some information regarding the issue.

vitejs/vite#22627 (comment)

[camc314]

What's the issue with printing the string across multipls lines vs the same line? - As per the minifier FAQ, this is done to minimize the out size.

Given the following input: export const FRAGMENT_TRANSFORM2 = TEST \n TEST \n TEST \n TEST;

Oxc minifies this to 61 bytes, and Terser minifies this to 64 bytes.

Oxc's miniications is an improvement vs oxc's.

oxc playground