issues
search
TooTallNate
/
gnode
Run node with ES6 Generators, today!
MIT License
248
stars
15
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Update example from co v4 changes
#23
techniq
closed
9 years ago
2
Fix fork not working correctly
#22
etiktin
opened
9 years ago
3
Fix `npm test` failing to run
#21
etiktin
closed
9 years ago
2
New Relic node module ETIMEDOUT
#20
guilhermesteves
closed
9 years ago
2
Scope issue for function expressions
#19
dominicbarnes
opened
9 years ago
1
Upgrade regenerator
#18
popomore
closed
9 years ago
12
[WIP] Cache regenerated files onto disk
#17
jonathanong
closed
9 years ago
0
generalize library?
#16
amasad
opened
10 years ago
2
Refactor for regenerator's breaking changes
#15
stephenmathieson
closed
10 years ago
2
facebook/regenerator's api changed
#14
stephenmathieson
closed
10 years ago
1
Update to Regenerator v0.6.3.
#13
benjamn
closed
10 years ago
3
cluster.isMaster returns true for forked processes
#12
oortlieb
opened
10 years ago
2
Add module caching
#11
agrieve
opened
10 years ago
1
Fix repl erroring on valid code.
#10
timoxley
closed
10 years ago
1
Make gnode -p &/or node -e work properly.
#9
timoxley
closed
10 years ago
3
Upgrade Regenerator to v0.4.1
#8
benjamn
closed
10 years ago
1
Anyway to run this with Nodemon
#7
DarrylD
closed
10 years ago
2
Never compile code that is already valid
#6
ForbesLindesay
closed
10 years ago
4
only use regenerator when necessary
#5
jonathanong
closed
10 years ago
6
Upgrade regenerator dependency to v0.3.2
#4
benjamn
closed
10 years ago
1
Stack traces line number are messed up
#3
TooTallNate
opened
11 years ago
3
gnode -p &/or node -e don't work properly
#2
TooTallNate
closed
10 years ago
0
what happens if i `require('gnode')` even if generators are already supported?
#1
jonathanong
closed
11 years ago
7