- 19 Sep, 2014 3 commits
-
-
Mithgol authored
-
Mithgol authored
-
Dane Springmeyer authored
-
- 15 Sep, 2014 2 commits
-
-
Updated NAN to 1.3.0
Mithgol authored -
King Koopa authored
-
- 05 Sep, 2014 2 commits
- 03 Sep, 2014 1 commit
-
-
drop support for Node.js 0.8.x branch
Mithgol authored
-
- 02 Sep, 2014 1 commit
-
-
Mithgol the Webmaster authored
-
- 01 Sep, 2014 1 commit
-
-
Mithgol the Webmaster authored
-
- 31 Aug, 2014 2 commits
- 27 Aug, 2014 2 commits
-
-
Mithgol the Webmaster authored
-
Mithgol the Webmaster authored
-
- 16 Aug, 2014 1 commit
-
-
Mithgol the Webmaster authored
-
- 06 Aug, 2014 17 commits
-
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
[Suggestion] Use NPM features to ensure correct node version
Dane Springmeyer authored -
Fix leak in complete() callback of Database.each()
Dane Springmeyer authored
-
- 05 Aug, 2014 1 commit
-
-
According to the readme: > The sqlite3 module works with Node.js v0.8.x, v0.10.x or v0.11.x (though only v0.11.13 and above). I propose the engines parameter be updated to be more specific, and that `engineStrict:true` is provided so that the node version should be enforced by npm when running `npm install` (https://www.npmjs.org/doc/files/package.json.html#enginestrict)
Hannah Wolfe authored
-
- 01 Aug, 2014 7 commits
-
-
another attempt to work around npm and ^ problem - refs https://github.com/npm/fstream/commit/f96c1b338148439e73f7e70ffbdc37e2759dfc68
Dane Springmeyer authored -
Conflicts: appveyor.yml
Dane Springmeyer authored -
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Dane Springmeyer authored
-
Nw 32bit fix
Dane Springmeyer authored -
Dane Springmeyer authored
-