Paulo De Mitri@paulogdm
with Express the request object contains the above information, which I can use to properly build a url (it lets me know whether to use "http" or "https"). this seems to be missing from Micro. how can I tell if the call was encrypted?
micro - initialisation
Hey, I was googling around for a good way to do a 'once off initialisation' before starting my app. My startup logic is async. Has anyone got any suggestions about how to go about this with Micro?
How to run Micro on Now V2
Ive written a small graphql service using micro (followed the example). It runs fine under micro-dev and micro on my localhost. It deploys and runs under Now V1 but doesn't run under Now V2. Im using the @now/node builder which reports a successful. But i get a 504: An error…
New library for Micro on AWS Lambda
We're open sourcing this new library for running Micro functions on AWS Lambda. We've been using it in production for a while and consider it stable for release to the world: https://github.com/nathancahill/aws-serverless-micro
npm i -g micro-dev - errors?
I figured I'd install micro-dev globally rather than every time in my repo, particularly as most of my micro-based projects are single files. But when I run the globally installed micro-dev in a directory with a single index.js (that contains a hello-world micro response), I get…
Unexpected JSON in logger
I often satisfy lambda requests with: but that function (defined in log.js), passes it to logResponse as seen below: which expects to parse it as a JSON object, and that therefore fails. please see attached picture below
TypeError: Chaining cycle detected for promise #<Promise>
I'm getting this error with a very short stack trace: "at process.internalTickCallback (internal/process/next_tick.js:77:7) and is emanating out of Micro. the error pops up on the call to runMicroTasks() and happens with both micro and micro-dev. I would post a picture here but…
N U R O ™·50d
Unable to exit Micro running in the background
Only started using now dev as of recently and I love it. However my bad habit of spamming Ctrl+C to exit/close the server has resulted in Micro not closing correctly/safely and as such now when the server is "closed" I can still go to http://localhost:3000 and it will still be…
Micro hangs up [SOLVED]
when I run npm start, I can run my lambda but at some point I want to terminate it with ^C... when I do I get this message: but micro never terminates. it just hangs I use to be able to hit ^c more times and it would (sort of) die but now that I'm running this under the VSCode…