wikimedia/mediawiki-extensions-VisualEditor
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/VisualEditor synced 2024-11-25 06:46:26 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Visual.../modules/parser/package.json

31 lines
639 B
JSON
Raw Normal View History

As much as I have loved writing Makefiles... I've replaced its functionality with package.json, mostly so we can avoid non-node dependencies. This is one of the recommended practices. We should consider moving tests/parser into modules/parser/tests, other node projects keep all module code in one directory. Explained in the README how to use npm to load the dependencies and run tests. Too bad about NODE_PATH... Don't try to find parserTests.txt in assorted places--if it isn't present, fetch from gerrit. You can symlink from core if you're developing on both parsers, and the fetch script will not overwrite. Use __dirname in parserTests.js to allow the script to run independent of current working directory. Change-Id: I4c8b884e91f4fdeae385c7697aff768bdd199dd5
2012-03-24 23:31:48 +00:00
{
"name": "mediawiki-parsoid",
"description": "Mediawiki parser for the VisualEditor.",
"version": "0.0.1",
"dependencies": {
"events": "0.x.x",
"jquery": "1.x.x",
"request": "2.x.x",
"querystring": "0.x.x",
"path": "0.x.x",
"jshashes": "0.x.x",
"optimist": "0.x.x",
"assert": "0.x.x",
"jsdom": "0.x.x",
Add tokenizer cache and clone token state on mutation * Added an LRU cache (using the lru-cache node module) for tokenizer output * Mutation of nested attributes now replaces the containers. A shallow copy of tokens is sufficient to isolate token transformations. Need to investigate if we can actually get away without isolation and re-transformation for most ordinary tokens. Change-Id: I9136b1d7a1fbcc538183a319d4ecaa290d616fdf
2012-04-18 12:30:59 +00:00
"pegjs": "0.x.x",
Big token transform framework overhaul part 2 * Tokens are now immutable. The progress of transformations is tracked on chunks instead of tokens. Tokenizer output is cached and can be directly returned without a need for cloning. Transforms are required to clone or newly create tokens they are modifying. * Expansions per chunk are now shared between equivalent frames via a cache stored on the chunk itself. Equivalence of frames is not yet ideal though, as right now a hash tree of *unexpanded* arguments is used. This should be switched to a hash of the fully expanded local parameters instead. * There is now a vastly improved maybeSyncReturn wrapper for async transforms that either forwards processing to the iterative transformTokens if the current transform is still ongoing, or manages a recursive transformation if needed. * Parameters for parser functions are now wrapped in abstract Params and ParserValue objects, which support some handy on-demand *value* expansions. Keys are always expanded. Parser functions are converted to use these interfaces, and now properly expand their values in the correct frame. Making this expansion lazier is certainly possible, but would complicate transformTokens and other token-handling machinery. Need to investigate if it would really be worth it. Dead branch elimination is certainly a bigger win overall. * Complex recursive asynchronous expansions should now be closer to correct for both the iterative (transformTokens) and recursive (maybeSyncReturn after transformTokens has returned) code paths. * Performance degraded slightly. There are no micro-optimizations done yet and the shared expansion cache still has a low hit rate. The progress tracking on chunks is not yet perfect, so there are likely a lot of unneeded re-expansions that can be easily eliminated. There is also more debug tracing right now. Obama currently expands in 54 seconds on my laptop. Change-Id: I4a603f3d3c70ca657ebda9fbb8570269f943d6b6
2012-05-10 08:04:24 +00:00
"lru-cache": "1.x.x",
Basic parser / serializer web service * After installing Parsoid (sudo npm install -g in modules/parser), run 'node server.js' from the api directory and navigate to http://localhost:8000/ and follow the directions. You can start to navigate the English wikipedia at http://localhost:8000/Main_Page, or manually enter wikitext or HTML DOM to convert. * Uses the express framework, could also use just connect * Uses the cluster module to manage workers per-core and restart those on failure Change-Id: I443f2996ed3df00826b038b7476a2f966ab0c425
2012-05-23 10:35:00 +00:00
"async": "0.x.x",
"express": "2.5.x"
As much as I have loved writing Makefiles... I've replaced its functionality with package.json, mostly so we can avoid non-node dependencies. This is one of the recommended practices. We should consider moving tests/parser into modules/parser/tests, other node projects keep all module code in one directory. Explained in the README how to use npm to load the dependencies and run tests. Too bad about NODE_PATH... Don't try to find parserTests.txt in assorted places--if it isn't present, fetch from gerrit. You can symlink from core if you're developing on both parsers, and the fetch script will not overwrite. Use __dirname in parserTests.js to allow the script to run independent of current working directory. Change-Id: I4c8b884e91f4fdeae385c7697aff768bdd199dd5
2012-03-24 23:31:48 +00:00
},
"devDependencies": {
"colors": "0.x.x",
"diff": "1.x.x",
"html5": "0.x.x"
},
"main": "mediawiki.parser.js",
"scripts": {
Parsoid: move tests/parser to modules/parser/test In preparation for the big extraction of Parsoid out of VisualEditor, we'll start by moving the tests into the parsoid location. Change-Id: I4a926ee4aad1490d4f769d44e91af80842b881f0
2012-07-25 00:22:45 +00:00
"pretest": "node test/fetch-parserTests.txt.js",
"test": "node test/parserTests.js"
As much as I have loved writing Makefiles... I've replaced its functionality with package.json, mostly so we can avoid non-node dependencies. This is one of the recommended practices. We should consider moving tests/parser into modules/parser/tests, other node projects keep all module code in one directory. Explained in the README how to use npm to load the dependencies and run tests. Too bad about NODE_PATH... Don't try to find parserTests.txt in assorted places--if it isn't present, fetch from gerrit. You can symlink from core if you're developing on both parsers, and the fetch script will not overwrite. Use __dirname in parserTests.js to allow the script to run independent of current working directory. Change-Id: I4c8b884e91f4fdeae385c7697aff768bdd199dd5
2012-03-24 23:31:48 +00:00
}
}
Reference in a new issue Copy permalink