Open JeanRemiDelteil opened 5 years ago
@JeanRemiDelteil just to be certain, this issue occurs with the latest npm
? Have you tried using a local build from the current master
of this repository?
For reference: DEP0066: OutgoingMessage.prototype._headers, OutgoingMessage.prototype._headerNames
@JeanRemiDelteil @grant I was able to reproduce this issue on Mac OS, using Node 12.3.1 and npm's clasp@2.1.0 I then used a local build from this repository and the deprecation warning no longer occured.
This issue is likely to be closed with next release of clasp.
Great !
Note: I've published @google/clasp@2.2
any updates on this? I'm still seeing "(node:...) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated"
@koconnor3 what version of nodejs and clasp are you using?
@koconnor3 what version of nodejs and clasp are you using?
my bad, looks like I had only updated clasp on my other machine 🤦♂️
Expected Behavior
No deprecation warrning when using
clasp push
Actual Behavior
when using
clasp push
we have a deprecation warrning on Node v12.3.1Steps to Reproduce the Problem
clasp push
in a projectSpecifications
node -v
): v12.3.1clasp -v
): 2.1.0