SOsonnyp·Jan 20, 2016
In Enable Node.js to Run with Microsoft's ChakraCore Enginezpao
spidernode
JavaScript2013–2016
zpao / spidernode · Archived
spidernode
A port of node.js using the SpiderMonkey JS engine instead of V8. [NO LONGER MAINTAINED]
10Distinct people
11Mentions
0Explicit recommenders
215GitHub stars
What to know before exploring
What it is
A port of node.js using the SpiderMonkey JS engine instead of V8. [NO LONGER MAINTAINED]
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- creationix/luvmonkey · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year11 dated mentions
Observed mentions: 2013-03-28 14:52:27 UTC to 2016-01-20 07:54:29 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
11 sourcesHere's Mozilla's effort to implement the V8 api on spidermonkey if anyone's curious:
https://github.com/zpao/spidernode
In Enable Node.js to Run with Microsoft's ChakraCore EngineThere used to be an Mozilla spidermonley based node.js too, though it isn't maintained atm.
https://news.ycombinator.com/item?id=2469786
https://github.com/zpao/spidernode
In Microsoft Edge's JavaScript engine to go open-sourceI don't. A lot of code out in the wild already relies on v8, and won't work with Chkara. Node 5 is up-to-date with v8. Though, I would like to see Mozilla devsvwpuld revives the unofficial spidermonkey Node.js support (https://news.ycombinator.com/item?id=2469786 , https://github.com/zpao/spidernode ).
In Microsoft Edge's JavaScript engine to go open-sourceI take it this is different from the NodeRED[0] thing IBM released a year or two ago? So, if node.js proper was closer to v8 HEAD, then they might find that the v8 team has recently been supportive of utilizing "precompiled scripts" (in v8 parlance). And I don't believe divorcing node from v8 is hard. Nobody is interested[1] (long term) in supporting such a divorce. For the most part, creating an API that would support both at the same time is maybe a month's worth of work at most.
[0] https://gigaom.com/2013/09/27/meet-node-red-an-ibm-project-t...
[1] https://github.com/zpao/spidernode
In Joyent Moves to Establish Node.js FoundationSadly dead - https://github.com/zpao/spidernode
In Introducing node-firefoxYou did have luvmonkey¹, and spidernode².
1: https://github.com/creationix/luvmonkey
2: https://github.com/zpao/spidernode
In Node.js Advisory Board"SpiderNode" [1] and "luvmonkey" [2] were two Node experiments using SpiderMonkey (from 2012). The first implemented V8's embedding API on top of SpiderMonkey. The second implemented libuv bindings in SpiderMonkey. Neither project was an official Mozilla project. Mozilla's SpiderMonkey team has (casually) discussed rebooting SpiderNode for server-side ES6 and asm.js support, but nothing is planned.
[1] https://github.com/zpao/spidernode
[2] https://github.com/creationix/luvmonkey
In Introducing Rec RoomIt's actually been done[1], to more or less success, but hasn't been kept up, and the differences in embedding SpiderMonkey vs V8 were cumbersome iirc. Not to mention compatibility with compiled modules. I was interested as E4X support would have been nicer earlier on, but it's surprising how quickly json has taken over.
[1] https://github.com/zpao/spidernode
In Node.js Tools for Visual StudioThe mozilla guys took a stab at creating a "spidernode" a while back:
https://github.com/zpao/spidernode
but then they dropped it.
In "Optimizations should be added to V8" for the asm.js subset of JavaScript