Avoid errors from the snippets being linted independently

…JavaScript code blocks

perl -pi -e 'BEGIN{undef $/;} s/```js#async:true/<!-- async:true -->\n```js/g;' `find documentation -name '*.md'`
perl -pi -e 'BEGIN{undef $/;} s/```js#evaluate:false/<!-- evaluate:false -->\n```js/g;' `find documentation -name '*.md'`
perl -pi -e 'BEGIN{undef $/;} s/```js#freshExpect:true/<!-- freshExpect:true -->\n```js/g;' `find documentation -name '*.md'`
perl -pi -e 'BEGIN{undef $/;} s/```js#skipBrowser:true/<!-- skipBrowser:true -->\n```js/g;' `find documentation -name '*.md'`

…avaScript

So that eslint-plugin-markdown can't tell they're JavaScript 😼

…ting

* master:
  Updated the changelog
  11.0.1
  Build unexpected.js
  Remove ad hoc disabling of the no-unexpected-multiline eslint rule
  Whoops, two of those had to be Buffer.alloc
  Fix lint
  new Buffer => Buffer.from
  Add mocha env to the eslint config
  eslint --fix .
  Add standard and prettier/standard
  Replace eslint-config-pretty-standard with eslint-config-prettier
  Disable no-unexpected-multiline so standard and prettier don't battle each other
  eslint --fix .
  Fix expect.promise#inspect tests
  Avoid deprecation warnings in node.js 10 because we have methods called inspect

* master:
  .eslintrc.js: Remove unnecessary parserOptions

…documentation -name '*.md'`

…ed-markdown to ^3.0.0

…d of in documentation/.eslintrc

Now that we can combine eslint and unexpected-markdown directives:

<!-- unexpected-markdown evaluate:false -->
<!-- eslint-skip -->