mysqljs/mysql

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

Open

#1655 opened on Mar 2, 2017

View on GitHub
 (22 comments) (4 reactions) (0 assignees)JavaScript (18,137 stars) (2,502 forks)batch import
help wanted

Description

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

Contributor guide

Tech stack
javascriptnodejs
Domain
backendbuild system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.js fundamentalsWebpack configurationMySQL basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
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.