mirrors
/
TiddlyWiki5
mirror of https://github.com/Jermolene/TiddlyWiki5
1
0
Fork 0
Code Issues Releases Wiki Activity
TiddlyWiki5/package.json

44 lines
1.1 KiB
JSON
Raw Normal View History

Initial package.json
2012-07-13 16:08:23 +00:00
{
"name": "tiddlywiki",
"preferGlobal": "true",
Update package.json for v5.3.4-prerelease
2024-01-17 11:51:51 +00:00
"version": "5.3.4-prerelease",
Initial package.json
2012-07-13 16:08:23 +00:00
"author": "Jeremy Ruston <jeremy@jermolene.com>",
Remove more pesky instances of "reusable"
2013-03-19 22:45:12 +00:00
"description": "a non-linear personal web notebook",
5.0.0-1
2013-08-26 20:45:20 +00:00
"contributors": [
Initial package.json
2012-07-13 16:08:23 +00:00
{
"name": "Jeremy Ruston",
"email": "jeremy@jermolene.com"
5.0.0-1
2013-08-26 20:45:20 +00:00
}
Initial package.json
2012-07-13 16:08:23 +00:00
],
"bin": {
Completed renaming cli.js to tiddlywiki.js
2012-07-18 10:50:48 +00:00
"tiddlywiki": "./tiddlywiki.js"
Initial package.json
2012-07-13 16:08:23 +00:00
},
Updates "main" in package.json Fixes require "Error: Cannot find module 'tiddlywiki'"
2014-01-13 18:29:22 +00:00
"main": "./boot/boot.js",
Initial package.json
2012-07-13 16:08:23 +00:00
"repository": {
"type": "git",
"url": "https://github.com/Jermolene/TiddlyWiki5.git"
},
"keywords": [
"tiddlywiki",
"tiddlywiki5",
"wiki"
],
Add eslint plus very tolerant starting config (#4872) * Add eslint plus very tolerant starting config Addresses GH #1865 This adds eslint as a developer dependency, plus a generated eslint config that doesn't take a very strong stance on much of anything. The goal here to get started using automated style checking, add eslint checking to the testing flow, and gradually introduce stricter checks over time. * eslint: Fix ecmaVersion See https://github.com/Jermolene/TiddlyWiki5/pull/4421#issuecomment-587002325, where @Jermolene declared TiddlyWiki targets EcmaScript 5
2020-10-26 17:52:25 +00:00
"devDependencies": {
Add keyword-spacing rule to .eslintrc.yml to reflect the project code style. (#6431) - Update .eslintignore to ignore "third party" code. - Add a "lint" script to package.json so `npm run lint` runs eslint on the repo.
2022-01-29 17:41:09 +00:00
"eslint": "^7.32.0"
Add eslint plus very tolerant starting config (#4872) * Add eslint plus very tolerant starting config Addresses GH #1865 This adds eslint as a developer dependency, plus a generated eslint config that doesn't take a very strong stance on much of anything. The goal here to get started using automated style checking, add eslint checking to the testing flow, and gradually introduce stricter checks over time. * eslint: Fix ecmaVersion See https://github.com/Jermolene/TiddlyWiki5/pull/4421#issuecomment-587002325, where @Jermolene declared TiddlyWiki targets EcmaScript 5
2020-10-26 17:52:25 +00:00
},
Initial package.json
2012-07-13 16:08:23 +00:00
"license": "BSD",
Correct package.json "engines" entry
2013-01-28 19:26:26 +00:00
"engines": {
Initial package.json
2012-07-13 16:08:23 +00:00
"node": ">=0.8.2"
Add keyword-spacing rule to .eslintrc.yml to reflect the project code style. (#6431) - Update .eslintignore to ignore "third party" code. - Add a "lint" script to package.json so `npm run lint` runs eslint on the repo.
2022-01-29 17:41:09 +00:00
},
"scripts": {
npm start should use mws-listen
2024-03-25 22:38:10 +00:00
"start": "node ./tiddlywiki.js ./editions/multiwikiserver --mws-listen",
Don't do full debug logging during tests
2024-03-20 15:12:35 +00:00
"test": "node ./tiddlywiki.js ./editions/test --verbose --version --build index && node ./tiddlywiki ./editions/multiwikiserver/ --mws-listen --mws-test-server http://127.0.0.1:8080/ --quit",
Chore: Add npm script for new core developers (#7539) * Update package.json * lint fix * chore: use node ./tiddlywiki.js instead of ./bin/serve.sh * Update package.json * Update package.json
2023-10-16 17:29:51 +00:00
"lint:fix": "eslint . --fix",
Add keyword-spacing rule to .eslintrc.yml to reflect the project code style. (#6431) - Update .eslintignore to ignore "third party" code. - Add a "lint" script to package.json so `npm run lint` runs eslint on the repo.
2022-01-29 17:41:09 +00:00
"lint": "eslint ."
Add dependencies to package.json This is needed in order for our CI to be able to run the tests
2024-01-02 14:47:32 +00:00
},
"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"
Initial package.json
2012-07-13 16:08:23 +00:00
}
5.0.0-1
2013-08-26 20:45:20 +00:00
}