Closed
Bug 1333116
Opened 8 years ago
Closed 8 years ago
Node v6 and related upgrades are causing rendering issues
Categories
(developer.mozilla.org Graveyard :: KumaScript, defect)
developer.mozilla.org Graveyard
KumaScript
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jwhitlock, Assigned: rjohnson)
References
Details
(Keywords: in-triage)
We recently updated the KumaScript engine from node v0.10 to node v6 (bug 1319259). The KumaScript tests passed, as well as manual rendering testing, but some issues are being exposed in production. This is a tracking bug for those issues.
The upgrades:
nodejs 0.10.26 -> 6.9.2
async 0.7.0 -> 2.1.4
ejs 0.6.1 -> 2.5.2
express 2.5.6 -> 4.14.0
feedparser 0.16.6 -> 1.1.5
fibers 1.0.1 -> 1.0.15
http-proxy 0.8.1 -> 1.15.2
memcached 0.2.8 -> 2.2.2
nconf 0.6.9 -> 0.8.4
newrelic 1.22.2 -> 1.34.0
node-statsd 0.0.7 -> 0.1.1
request 2.9.100 -> 2.79.0
sax 0.5.x -> 0.6.1 (implicit requirement)
underscore 1.5.0 -> 1.8.3
winston 0.7.3 -> 2.3.0
nodeunit 0.6.4 -> 0.10.2
jshint 0.5.7 -> 2.9.4
Replaced:
express.app.logger with morgan 1.7.0
Removed:
http-proxy 0.8.1
docco 0.3.0
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → rjohnson
Status: NEW → ASSIGNED
Reporter | ||
Comment 1•8 years ago
|
||
All known issues fixed. Good work rjohnson!
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•