You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In connect 2.3.7 the send function was split into a separate module (senchalabs/connect@3ea7fa2), which breaks connect-gzip. This is unfortunate because connect-gzip specifies a very liberal version range in package.json, so all fresh installs of connect-gzip are broken right now.
My recommendation is to pin the connect dependency at a specific version:
... then release a new version of connect-gzip asap.
Then later when we're ready to use the new connect API, we can pin it at whatever is the latest version at that point. It's a little more housekeeping, but much safer.
And yes, this just bit me upon upgrading a production server :/
The text was updated successfully, but these errors were encountered:
In connect 2.3.7 the
send
function was split into a separate module (senchalabs/connect@3ea7fa2), which breaksconnect-gzip
. This is unfortunate becauseconnect-gzip
specifies a very liberal version range inpackage.json
, so all fresh installs ofconnect-gzip
are broken right now.My recommendation is to pin the
connect
dependency at a specific version:... then release a new version of
connect-gzip
asap.Then later when we're ready to use the new connect API, we can pin it at whatever is the latest version at that point. It's a little more housekeeping, but much safer.
And yes, this just bit me upon upgrading a production server :/
The text was updated successfully, but these errors were encountered: