rewrote our lambda deploy to 'pure' node (no shelling out) and roughly halved our deploy time.
21 http endpoints: 7s! zero downtime.pic.twitter.com/EG7s5c8EzS
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
That is still pretty impressive for 21 funcs. Webpack? What zip lib you using? I likely want to steal it for shep :)
No bundling but sorely tempted often. We keep our zip payloads sub 5mb, zip/upload in parallel (npm pkg zipit)
nice. had not seen that package. We say payload sizes go way down with webpack. A sampling of current funcs:https://www.dropbox.com/s/4xfmwiu7m2l8jgv/Screenshot%202017-05-17%2015.31.23.png?dl=0 …
ya that's rad --I def want to do this for our production lambdas
I should note we don't minify (yet). I'd actually like to switch to rollup. Or for webpack to get proper scope hoist. Whichever comes first
yes thats another thing I'd like to put into the prod lambdas (but leave the staging ones alone for debug ease)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.