- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Feb 2016 21:57:42 +0000
- To: public-secondscreen@w3.org
mfoltzgoogle has just created a new issue for https://github.com/w3c/presentation-api: == travis-cl complains about obsolete nvm version == When publishing the last working draft, travis-cl complained that the version of `nvm` is out of date: ``` 0.94s$ nvm install 0.10 ######################################################################## 100.0% Now using node v0.10.42 npm WARN deprecated This version of npm lacks support for important features, npm WARN deprecated such as scoped packages, offered by the primary npm npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the npm WARN deprecated latest stable version. To upgrade to npm@2, run: npm WARN deprecated npm WARN deprecated npm -g install npm@latest-2 npm WARN deprecated npm WARN deprecated To upgrade to the latest stable version, run: npm WARN deprecated npm WARN deprecated npm -g install npm@latest npm WARN deprecated npm WARN deprecated (Depending on how Node.js was installed on your system, you npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if npm WARN [35mdeprecated on Windows, run them from an Administrator prompt.) npm WARN deprecated npm WARN deprecated If you're running the version of npm bundled with npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS npm WARN deprecated will be bundled with a version of npm@2, which has some small npm WARN deprecated backwards-incompatible changes made to `npm run-script` and npm WARN deprecated semver behavior. ``` I am not sure how to update the version of `nvm` run in the container but can investigate. On the other hand, the only thing our travis-cl script does is to run `curl`; I am wondering if we need to mess with node.js at all. Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/265 using your GitHub account
Received on Thursday, 11 February 2016 21:57:56 UTC