mysqljs/mysql

NodeJs API + Webpack 2 Production Builds = Error: Received packet in the wrong sequence

Open

#1,655 创建于 2017年3月2日

在 GitHub 查看
 (22 评论) (4 反应) (0 负责人)JavaScript (18,137 star) (2,502 fork)batch import
help wanted

描述

Hey - I love this module, thanks. I would love to use it in a nodeJs Api we are building, however I am running into an {odd?} issue where I am unable to move my code into a production environment. Every time I compile with webpack without setting devtool="eval" causes any attempt to make a connection result in an Error: Received packet in the wrong sequence. My understanding is the devtool option controls if and how Source maps are generated from the compile process. I am not sure why exactly this would effect the execution of code, no errors result from actual compiling. Would love to know if there is some setting I am missing or way to get this working. Thanks

贡献者指南

技术栈
javascriptnodejs
领域
backendbuild system
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Node.js fundamentalsWebpack configurationMySQL basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Investigate why setting webpack's devtool to 'eval' resolves the 'Received packet in the wrong sequence' error. Look into the mysql module's packet handling in lib/protocol/ to see if it relies on function names or eval friendly constructs that get altered by minification. Check the comments for any reported solutions with specific webpack versions or plugins. Reproduce the issue with a minimal setup and test different devtool values to isolate the cause.