mysqljs/mysql

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

Open

#1 655 ouverte le 2 mars 2017

Voir sur GitHub
 (22 commentaires) (4 réactions) (0 assignés)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

Guide contributeur

Stack technique
javascriptnodejs
Domaine
backendbuild system
Type d'issue
bug
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-2 days
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
stale
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
Node.js fundamentalsWebpack configurationMySQL basics
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
35
Direction de recherche
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.