W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2017

Re: [webrtc-stats] upgrade to Node 8 (respec now uses async/await)

From: Vivien Lacourba via GitHub <sysbot+gh@w3.org>
Date: Fri, 20 Oct 2017 14:25:28 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-338221895-1508509527-sysbot+gh@w3.org>
`webrtc-stats.html` has `<script class="remove" src="https://www.w3.org/Tools/respec/respec-w3c-common">` so it uses the latest published respec version (currently 1.7.1).

@dontcallmedom noticed recent travis builds were failing because respec now uses `async` and Travis was still running Node 6.

This was the error he got from https://travis-ci.org/w3c/webrtc-stats/builds/290375085:
```
node support/respec/tools/respec2html.js -e --src file://`pwd`/webrtc-stats.html --out build/output.html
/home/travis/build/w3c/webrtc-stats/support/respec/tools/respecDocWriter.js:31
async function writeTo(outPath, data) {
^^^^^^^^
SyntaxError: Unexpected token function
```

Switching to Node 8 fixes this particular issue but repesc still fails https://travis-ci.org/w3c/webrtc-stats/builds/290456592:
```
node support/respec/tools/respec2html.js -e --src file://`pwd`/webrtc-stats.html --out build/output.html
😱 ReSpec error: [object Object]
make: *** [build/output.html] Error 1
```

Good or bad news we are not the only one having issues
https://github.com/w3c/spec-generator/pull/44#issuecomment-338206307

@marcoscaceres, Dom noticed a `ReferenceError: respecConfig is not defined` error in the console.

-- 
GitHub Notification of comment by vivienlacourba
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/252#issuecomment-338221895 using your GitHub account
Received on Friday, 20 October 2017 14:25:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 October 2019 15:14:56 UTC