<Collapsibletitle="NS_ERROR_CORRUPTED_CONTENT error in console">
<p>→ See also "The pipeline passed but the Wiki is not visible under the url" as these errors can be connected.</p>
<p> This error for css and js files can be the result of wrong <b>rollupOptions</b> in for the build, to be specific wrong <b>output</b> and <b>assetFileNames</b> options and possibly wrong/empty <b>css</b> options in your vite.config.js. </p>
<h6>Example</h6>
<p>In our case, we had the following code on our vite.config.js</p>
<p> Our <b>css</b> options were empty, which could also have played a factor for the css files.</p>
<Code>
<p>css: {</p>
<p>preprocessorOptions: {</p>
<p>css: {</p>
<p> //javascriptEnabled: true, // Enable JavaScript in CSS (useful for certain CSS preprocessor plugins)</p>
<p>}}},</p>
</Code>
</Collapsible>
</div>
<divclassName="filterable all console">
<Collapsibletitle="Blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff) (Firefox)">
<p>→ See also "Refused to apply style from <<css file>> because its MIME type ('text/html') is not a supported stylesheet MIME type, strict MIME checking is enabled (Edge)"</p>
<p>This error could </p>
</Collapsible>
</div>
<divclassName="filterable all console">
<Collapsibletitle="Refused to apply style from <<css file>> because its MIME type ('text/html') is not a supported stylesheet MIME type, strict MIME checking is enabled (Edge)">
<p>→ See also "Blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff) (Firefox)"</p>
<p>This error could </p>
</Collapsible>
</div>
<divclassName="filterable all react type">
<Collapsibletitle="Type 'undefined' cannot be used as an index type">