Unix与Win10下Svelte打包换行符不一致问题解决方案求助

I’ve run into this exact cross-platform newline quirk with Svelte before—here’s how you can force consistent \n\n line breaks in your bundled code, no matter if you’re building on Windows or Unix:

1. Set Svelte Compiler’s newline Option (Recommended) #

Svelte’s compiler has a built-in setting to lock in the newline character used in output. Add this configuration to your svelte.config.js:

import { vitePreprocess } from '@sveltejs/vite-plugin-svelte';

export default {
  preprocess: vitePreprocess(),
  compilerOptions: {
    newline: 'lf' // Forces Unix-style LF (\n) instead of OS-specific line breaks
  }
};

This tells Svelte to always generate "\n\n" in createText calls, eliminating the cross-platform discrepancy entirely.

2. Preprocess Components to Normalize Line Breaks #

If the compiler option alone doesn’t resolve the issue, add a preprocessing step to convert any CRLF (\r\n) line breaks in your .svelte files to LF (\n) before compilation:

import { vitePreprocess } from '@sveltejs/vite-plugin-svelte';

export default {
  preprocess: [
    // Custom preprocessor to standardize line breaks
    {
      markup({ content }) {
        return {
          code: content.replace(/\r\n/g, '\n')
        };
      }
    },
    vitePreprocess()
  ],
  compilerOptions: {
    newline: 'lf'
  }
};

This ensures hardcoded whitespace in your components is consistent before the compiler processes them.

3. Enforce LF Across Your Project #

For extra safety, lock in LF line breaks at the repo level:

• Add a .gitattributes file to force Git to use LF for all files:

  * text=auto eol=lf
  

• Use cross-env in your package.json scripts to avoid Windows-specific environment quirks:

  "scripts": {
    "build": "cross-env NODE_ENV=production svelte-kit build"
  }
  

Why This Happens #

Svelte defaults to using the operating system’s native line break (os.EOL) when generating text nodes in bundled code. Windows uses CRLF (\r\n), Unix uses LF (\n), and this whitespace difference can break CSS layout logic that relies on consistent spacing—like your tree component’s appearance.

After applying these fixes, rebuild your Windows bundle; the createText calls will match the Unix version’s "\n\n" format, and your tree component will look identical across platforms.

内容的提问来源于stack exchange，提问作者Serg Alekseev