Bug report

Mb for nuxt asyncData api, because waitFor not working for this
Something like this

export default function (waiter, func) {
  return async (...args) => {
    const { app } = args[0];

    try {
      app.wait.start(waiter);
      return await func.apply(this, args);
    } finally {
      app.wait.end(waiter);
    }
  };
};

Or if vue-wait have this function, sorry a

As in subtitle, investigate, wrong detection of repository main language ( is Swift not the Makefile).

In IE11, the spinner is positioned at the top of whatever container you place it in. In Chrome and FireFox, the spinner is always positioned in the center of the container.

IE11:

Chrome:
![image](https://user-images.githubusercontent.com/29128205/56240985-b7e7e400-6062-11e9-8122-5

See discussion end of #662

logging explicit instructions to install @loaders.gl/polyfills if polyfills are detected as missing would certainly help anyone else who may find themselves facing similar issues.

Core could e.g. look for TextDecoder on global scope and issue a warning.

(In the yet unmerged tantivy branch) content.query returns a sequence of document objects, which can be nicer to use, for example, to get the uuid of a document, one uses doc:get_first(content.fields.uuid), a possible alternative would be doc.uuid:get_first()

Hi!

I was curious if there was a reason why the internal API wasn't used? Was it to simplify usage, or because the actual lib API is kinda hard to figure out? ;)

(It took me a while to get it working as expected)

const documentation = require("documentation");

documentation.build([
  "./path/to/file.js",
], {
  github: true,
}, (err, comments) => {
  console.log(
    docu