Next.js 14.0.4生产模式MySQL包序列错误及配置咨询

问题描述 #

我的Next.js项目在开发模式下运行正常，但执行build后启动生产模式时，出现如下错误：

Error: Received packet in the wrong sequence.{
  e: Error: Received packet in the wrong sequence.
      at a._parsePacket (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:50:90760)
      at E._parsePacket (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:50:85839)
      at E.write (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:50:80036)
      at a.write (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:50:87298)
      at Socket.<anonymous> (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:50:55253)
      at Socket.<anonymous> (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:50:54362)
      at Socket.emit (node:events:519:28)
      at addChunk (node:internal/streams/readable:559:12)
      at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
      at Readable.push (node:internal/streams/readable:390:5)
      --------------------
      at a._enqueue (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:50:88666)
      at a.handshake (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:50:87421)
      at A.connect (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:50:56118)
      at /Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:37:7179
      at new Promise (<anonymous>)
      at u.acquireRawConnection (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:37:7057)
      at create (/Users/callpro/lime-dashboard-v2/.next/server/chunks/4679.js:5:874)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    code: 'PROTOCOL_INCORRECT_PACKET_SEQUENCE',
    fatal: true
  }
}

配置optimization:{minimize:false}的方法 #

在项目根目录的next.config.js文件中，通过webpack配置项修改优化参数：

/** @type {import('next').NextConfig} */
const nextConfig = {
  webpack: (config) => {
    // 关闭生产构建的代码压缩
    config.optimization.minimize = false;
    return config;
  },
};

module.exports = nextConfig;

说明 #

• 该配置会禁用Next.js生产构建时的代码压缩功能，可避免因压缩导致部分依赖库（如数据库驱动）出现协议包序列错误。
• 注意：关闭压缩会使构建产物体积显著增大，仅建议作为临时排查方案。后续需定位具体引发问题的依赖，通过webpack的minimizer配置单独排除该依赖的压缩处理，以兼顾性能与功能正常。

内容的提问来源于stack exchange，提问作者Erdene Vvl