sapper export: "UnhandledPromiseRejectionWarning: Error: Cannot add to a closed queue"

[btakita]

This is due to not waiting for all requests to finish in a promise.

See https://github.com/sveltejs/sapper/blob/master/src/api/export.ts#L176

[halfnelson]

This was clobbered by #641
the older code use q.add which allowed q.close to do the promise.all.

[kmelve]

We're hit by this as well, making it impossible to deploy our Sapper-starter on Netlify as a static site. It can be reproduced by deploying it through sanity.io/create.

It seems that async stuff in prefetch is the culprit? E.g https://github.com/sanity-io/sanity-template-sapper-blog/blob/master/template/web/src/routes/blog/%5Bslug%5D.svelte

[btakita]

@kmelve I manually go into the sapper source & modify the _export function in node_modules/sapper/dist/export.js to make the export work for now. Hopefully this will be fixed soon.

[btakita]

I created a temporary version that fixes this issue & #688

Use the following in your package.json

"sapper": "btakita/sapper#0.27.0-hotfix"

[kmelve]

Excellent @btakita – tnx 🙌

[antony]

@kmelve I also believe there is an issue in the default configuration for the deployed app in your sapper starter - even with this hotfix the deploy will fail.

To deploy correctly you need to change the deploy directory from __sapper__/export to web/__sapper__/export.