1
0
mirror of https://github.com/Jermolene/TiddlyWiki5 synced 2024-11-17 23:34:50 +00:00
TiddlyWiki5/package.json

44 lines
987 B
JSON
Raw Normal View History

2012-07-13 16:08:23 +00:00
{
"name": "tiddlywiki",
"preferGlobal": "true",
"version": "5.3.4-prerelease",
2012-07-13 16:08:23 +00:00
"author": "Jeremy Ruston <jeremy@jermolene.com>",
"description": "a non-linear personal web notebook",
2013-08-26 20:45:20 +00:00
"contributors": [
2012-07-13 16:08:23 +00:00
{
"name": "Jeremy Ruston",
"email": "jeremy@jermolene.com"
2013-08-26 20:45:20 +00:00
}
2012-07-13 16:08:23 +00:00
],
"bin": {
"tiddlywiki": "./tiddlywiki.js"
2012-07-13 16:08:23 +00:00
},
"main": "./boot/boot.js",
2012-07-13 16:08:23 +00:00
"repository": {
"type": "git",
"url": "https://github.com/Jermolene/TiddlyWiki5.git"
},
"keywords": [
"tiddlywiki",
"tiddlywiki5",
"wiki"
],
"devDependencies": {
"eslint": "^7.32.0"
},
2012-07-13 16:08:23 +00:00
"license": "BSD",
2013-01-28 19:26:26 +00:00
"engines": {
2012-07-13 16:08:23 +00:00
"node": ">=0.8.2"
},
"scripts": {
"dev": "node ./tiddlywiki.js ./editions/tw5.com-server --listen",
"test": "node ./tiddlywiki.js ./editions/test --verbose --version --build index",
"lint:fix": "eslint . --fix",
"lint": "eslint ."
},
"dependencies": {
MWS: Add support for node-sqlite-wasm alongside better-sqlite3 (#7996) * Switch from better-sqlite3 to node-sqlite3-wasm Seems to be slower, but might make cloud deployments easier by not having any binary dependencies * More logging * Temporarily use a memory database We will make this configurable * Revert "More logging" * Resume loading demo tiddlers * Cache prepared statements Gives a 20% reduction in startup time on my machine * Some more logging * Update package-lock * More logging * Route regexps should allow for proxies that automatically decode URLs Astonishingly, Azure does this * Go back to a file-based database * Less logging * Update package-lock.json * Simplify startup by not loading the docs edition * Tiddler database layer should mark statements as having been removed * Re-introduce better-sqlite3 * Make the SQLite provider be switchable * Support switchable SQL engines I am not intending to make this a long term feature. We will choose one engine and stick with it until we choose to change to another. * Adjust dependency versions * Setting up default engine * Make transaction handling compatible with node-sqlite3-wasm https://github.com/tndrle/node-sqlite3-wasm doesn't have transaction support so I've tried to implement it using SQL statements directly. @hoelzro do you think this is right? Should we be rolling back the transaction in the finally clause? It would be nice to have tests in this area... I looked at better-sqlite3's implementation - https://github.com/WiseLibs/better-sqlite3/blob/master/lib/methods/transaction.js * Default to better-sqlite3 for compatibility after merging
2024-02-22 11:57:41 +00:00
"better-sqlite3": "^9.4.3",
"node-sqlite3-wasm": "^0.8.10"
2012-07-13 16:08:23 +00:00
}
2013-08-26 20:45:20 +00:00
}