Arkadiy Kukarkin

hi @mroth, I am seeing this behavior with my symlinked golang repos, did a fix ever get committed somewhere? happy to look but don't want to replicate work

Hmm still seeing this behavior rebuilt against golang 1.7.1, though I actually don't know enough about go dependency mgmt to know if this pulled in the latest `os`

another suggestion I would make would be to add the needed plugin to package.json/serverless.yml in the template so the plugin install step is not necessary

@medikoo thanks for your reply, my apologies if the original report came off as demanding, the interlocking concerns here created a fairly frustrating situation to diagnose, so I spoke more...

Finally, on a really high level, I feel that working towards a uniform interface for serverlesss function deployment across providers would be a great boon to everybody in the field...

another small note, the error message links to "https://www.serverless.com/framework/docs/providers/aws/guide/plugins#extending-validation-schema", which is housed under /providers/aws, furthering the confusion about whether the provider I'm using is supported

the simplest solution here is to use `history.replaceState` so there's no "back" history entry to go back to

reworking history handling will also affect https://github.com/ipfs-shipyard/peer-pad/issues/311

Stack Overflow's [PageDown](https://github.com/StackExchange/pagedown) seems to be the standard here that being said I think this is out of scope for our product vision

this could be good -- tbh I mostly use it in the 1up view because my eyes read markdown better than the formatted view at this point: so it looks...