Le 12/09/2021 à 19:20, Julien Puydt a écrit : > Hi > > Le dim. 12 sept. 2021 à 18:39, Yadd <[email protected] > <mailto:[email protected]>> a écrit : > > Le 12/09/2021 à 18:35, Pirate Praveen a écrit : > > > > With nodejs supporting ESM natively, we should try to avoid as much of > > build steps as possible. > > You're right, but for now this avoid to downgrade updated packages (like > node-strip-json-comments which broke eslint) > > > You'll notice that before uploading the breaking > node-strip-json-comments, I did write to this list to ask for advice, > and uploaded a -1 which could still be required (but not imported, > breaking upstream in a way). > > And the sound advice was: follow upstream. So I uploaded -2 which broke > requiring deps; but could be imported like upstream meant. > > It we had something automatically doing the require-and-import trick, > that could be a temporary solution. Very very temporary. But this > workaround is manual and goes in the wrong direction, so I'm voting > against it. It looks like it could silently build up a technical debt... > until shit hits the fan (a when, not an if), then we'll have to foot the > bill. > > J. Puydt
You'll notice that I didn't fault anyone, I just tried not to let other groups get stuck with our updates. I think I did something clean that avoids breaking other packages until nodejs is updated and keeps the upstream format. So now I will avoid fixing bugs other than what I generated. -- Pkg-javascript-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
