Sapper: v0.13.0 __sapper__ EventStream seems to be borked

Created on 1 Jun 2018  路  1Comment  路  Source: sveltejs/sapper

It's dumping null messages every so many milliseconds.

See screen recordings:

I went back and forth determining if it was my project or could be reproduced in https://github.com/sveltejs/sapper-template <- quick note, it can't be reproduced UNLESS YOU UPDATE sapper-template to [email protected]. Right now it's on v .12: https://github.com/sveltejs/sapper-template/blob/master/package.json#L17

Once you update the Sapper version, sapper-template EventStream __sapper__ network connection gets borked too.

Most helpful comment

Absolute facepalm. I rewrote some stuff for 0.13 to break some CLI functionality out into an API that could be used by other clients (i.e. Sapper Studio), and managed to write the following code:

setInterval(() => {
  this.send(null);
}); // <-- look ma, no second argument!

Surprised TypeScript didn't yell at me. Fixed in 0.13.1.

>All comments

Absolute facepalm. I rewrote some stuff for 0.13 to break some CLI functionality out into an API that could be used by other clients (i.e. Sapper Studio), and managed to write the following code:

setInterval(() => {
  this.send(null);
}); // <-- look ma, no second argument!

Surprised TypeScript didn't yell at me. Fixed in 0.13.1.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Rich-Harris picture Rich-Harris  路  3Comments

SARFEX picture SARFEX  路  3Comments

milosdjakovic picture milosdjakovic  路  3Comments

mylastore picture mylastore  路  3Comments

Rich-Harris picture Rich-Harris  路  4Comments