v2.6.X打包是在rendering chunks 卡住

[1770301860]

Describe the bug

使用2.6.x版本打包时 在 rendering chunks 卡住 内存占用突然变得很高 然后就降低了 然后一直卡住

Reproduction

。。。

System Info

。。。。

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[github-actions]

Hello @1770301860. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[P-der]

mark

[sanyuan0704]

可以给个例子复现下吗？

[lincenying]

升级完之后, 我的也卡住了, 原因是用element-ui, 如果你也用了element-ui, 或者element-plus的话, 手动把node_modules/element-ui/lib/theme-chalk/*.css 里的@charset "UTF-8";删了

[P-der]

可以给个例子复现下吗？
https://github.com/P-der/vite-build 我尝试创建了一个，你可以试一下

[shigma]

我这也确实出现了这种问题。

[BinGarfield]

I have the same problem here....
system: centos 7, 8G
the development environment is normal, but it gets stuck when you build...

[BinGarfield]

package.json

[kensmaster]

lincenying说的对

[junbinding]

暂时还原到 2.5.10 吧

[iamiota]

Configuring this can temporarily solve the memory problem

export default defineConfig({
  css: {
    preprocessorOptions: {
      scss: {
        charset: false
      }
    }
  }
})

element-plus/element-plus#3219 (comment)

[ErHu1993]

Configuringminify: false in build can temporarily solve

export default defineConfig({
  css: {
    preprocessorOptions: {
      scss: {
        charset: false
      }
    }
  },
  build: {
    minify: false
  }
})

[alvinindra]

Configuringminify: false in build can temporarily solve

export default defineConfig({
  css: {
    preprocessorOptions: {
      scss: {
        charset: false
      }
    }
  },
  build: {
    minify: false
  }
})

But your script will bigger size and we need to minify it

[ErHu1993]

Yes, its not the best way 🙁

[john-keith]

the same question i've met 🙁

[menghany]

the same question when i use ant design vue 3.x

[john-keith]

the same question when i use ant design vue 3.x

yesterday i degrade the vite's version to 2.5.x without this problem yet

[menghany]

the same question when i use ant design vue 3.x

yesterday i degrade the vite's version to 2.5.x without this problem yet

I also temporarily reverted to the 2.5.10

[alvinindra]

the same question when i use ant design vue 3.x

yesterday i degrade the vite's version to 2.5.x without this problem yet

I also temporarily reverted to the 2.5.10

I solve the problem with this. This is ignore the charset problem. #5833

  css: {
    postcss: {
      plugins: [
          {
            postcssPlugin: 'internal:charset-removal',
            AtRule: {
              charset: (atRule) => {
                if (atRule.name === 'charset') {
                  atRule.remove();
                }
              }
            }
          }
      ],
    },
}

[lincenying]

postcss.config.js

var charsetRemoval = () => {
    return {
        postcssPlugin: 'internal:charset-removal',
        AtRule: {
            charset: atRule => {
                if (atRule.name === 'charset') {
                    atRule.remove()
                }
            }
        }
    }
}

module.exports = () => {
    return {
        plugins: [
            //其他postcss插件,
            charsetRemoval()
        ]
    }
}

直接放vite.config.js里好像和postcss.config.js有冲突, 导致postcss.config.js里的插件不生效

[gluck]

FYI as per evanw/esbuild#1862 upgrading to esbuild 0.14.6 fixed this for me (charset removal config no longer required)

[xiangqunXiao]

你可以分享你完整的 postcss 配置和 vite 配置吗？我试了还是无效

[sapphi-red]

Closing as it seems there was a bug in esbuild which is now fixed. #5597 (comment)