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

30 lines
653 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",
Biggish token transform system refactoring * All parser pipelines including tokenizer and DOM stuff are now constructed from a 'recipe' data structure in a ParserPipelineFactory. * All sub-pipelines of these can now be cached * Event registrations to a pipeline are directly forwarded to the last pipeline member to save relatively expensive event forwarding. * Some APIs for on-demand expansion / format conversion of parameters from parser functions are added: param.to('tokens/expanded', cb) param.to('text/wiki', cb) (this does not work yet) All parameters are additionally wrapped into a Param object that provides method for positional parameter naming (.named() or conversion to a dict (.dict()). * The async token transform manager is now separated from a frame object, with the frame holding arguments, an on-demand expansion method and loop checks. * Only keys of template parameters are now expanded. Parser functions or template arguments trigger an expansion on-demand. This (unsurprisingly) makes a big performance difference with typical switch-heavy template systems. * Return values from async transforms are no longer used in favor of plain callbacks. This saves the complication of having to maintain two code paths. A trick in transformTokens still avoids the construction of unneeded TokenAccumulators. * The results of template expansions are no longer buffered. * 301 parser tests are passing Known issues: * Cosmetic cleanup remains to do * Some parser functions do not support async expansions yet, and need to be modified. Change-Id: I1a7690baffbe8141cadf67270904a1b2e1df879a
2012-04-25 14:35:59 +00:00
"lru-cache": "1.x.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": {
"coffee-script": "1.x.x",
"colors": "0.x.x",
"diff": "1.x.x",
"html5": "0.x.x"
},
"main": "mediawiki.parser.js",
"scripts": {
"pretest": "node ../../tests/parser/fetch-parserTests.txt.js",
"test": "node ../../tests/parser/parserTests.js"
}
}
Reference in a new issue Copy permalink