Yves M.

Just a simple remark, maybe we can use something easier to parse like a custom `nvm` field in `package.json`: ```json { "nvm" : { "use" : "8.10.0" } } ```...

@edwmurph many popular tools like [babel](https://babeljs.io/docs/usage/babelrc/#use-via-packagejson), [eslint](https://eslint.org/docs/user-guide/configuring), [jest](https://facebook.github.io/jest/docs/en/configuration.html), etc. allows the configuration to be embeded in `package.json`.. That allows a simpler repository structure without a lot of hidden/rc files (`.editorconfig`,...

Ok so `.npmrc` within `package.json` should have [it's own issue](https://github.com/creationix/nvm/issues/1778). Sorry for the digression 😉

@kt3k I ran in the same issue, thank you so much for the `.default`workarround 👍

My `babel-core` version is actually 6.14.0 (I'm using `babel-cli` 6.14.0)

This looks like more to be a problem with VS Code 🤔

@[bittrance](https://github.com/bittrance) do you want admin access to this repository? 🤔 I'm not using Azure anymore and I will not be able to maintain this project anymore.. But why not transferring...

@techniq did you found a workaround? Feel free to submit a PR

@techniq do you think if we return the raw `Buffer` that may helps? See in [OutgoingMessage.js](https://github.com/yvele/azure-function-express/blob/f52b83a5659d9dc8cfb65fbb15227414909caf6b/src/OutgoingMessage.js#L9-L16): ```js /** * @param {Object|string|Buffer} body Express/connect body object * @param {string} encoding *...

### Diagnostic I've overwritten the internal `writeHead` method to setup `context.res.headers` (specific to Azure Functions) but it's specific to node 6. https://github.com/yvele/azure-function-express/blob/2bd90411b20480f2e430d730b638974d3391e671/src/OutgoingMessage.js#L35-L45 Node 8~10 doesn't have this internal `writeHead` method...