npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

parsoid-jsapi

v0.0.1

Published

Parsoid JSAPI

Downloads

4

Readme

Parsoid JSAPI

Build Status

Usage of the JavaScript API

This file describes usage of Parsoid as a standalone wikitext parsing package, in the spirit of mwparserfromhell. This is not the typical use case for Parsoid; it is more often used as a network service. See the HTTP API guide or Parsoid service on the wiki for more details.

These examples will use the prfun library and ES6 generators in order to fluently express asynchronous operations. The library also exports vanilla Promises if you wish to maintain compatibility with old versions of node at the cost of a little bit of readability.

Since many methods in the API return Promises, we've also provided a Promise-aware REPL, that will wait for a promise to be resolved before printing its value. This can be started from the shell using:

node -e 'require("parsoid-jsapi").repl()'

Use "./" instead of "parsoid" if you are running this from a checked-out repository. Code examples below which contain lines starting with > show sessions using this REPL. (You may also wish to look in tests/mocha/jsapi.js for examples using a more traditional promise-chaining style.)

Use of Parsoid as a wikitext parser is straightforward (where text is wikitext input):

#/usr/bin/node --harmony-generators
var Promise = require('prfun');
var Parsoid = require('parsoid-jsapi');

var main = Promise.async(function*() {
	var text = "I love wikitext!";
	var pdoc = yield Parsoid.parse(text, { pdoc: true });
	console.log(pdoc.document.outerHTML);
});

// start me up!
main().done();

As you can see, there is a little bit of boilerplate needed to get the asynchronous machinery started. The body of the main() method can be replaced with your code.

The pdoc variable above holds a PDoc object, which has helpful methods to filter and manipulate the document. If you want to access the raw Parsoid DOM, however, it is easily accessible via the document property, as shown above, and all normal DOM manipulation functions can be used on it (Parsoid uses domino to implement these methods). Be sure to call update() after any direct DOM manipulation. PDoc is a subclass of PNodeList, which provides a number of useful access and mutation methods -- and if you use these you won't need to manually call update(). These provided methods can be quite useful. For example:

> var text = "I has a template! {{foo|bar|baz|eggs=spam}} See it?\n";
> var pdoc = yield Parsoid.parse(text, { pdoc: true });
> console.log(yield pdoc.toWikitext());
I has a template! {{foo|bar|baz|eggs=spam}} See it?
> var templates = pdoc.filterTemplates();
> console.log(yield Promise.map(templates, Parsoid.toWikitext));
[ '{{foo|bar|baz|eggs=spam}}' ]
> var template = templates[0];
> console.log(template.name);
foo
> template.name = 'notfoo';
> console.log(yield template.toWikitext());
{{notfoo|bar|baz|eggs=spam}}
> console.log(template.params.map(function(p) { return p.name; }));
[ '1', '2', 'eggs' ]
> console.log(yield template.get(1).value.toWikitext());
bar
> console.log(yield template.get("eggs").value.toWikitext());
spam

Getting nested templates is trivial:

> var text = "{{foo|bar={{baz|{{spam}}}}}}";
> var pdoc = yield Parsoid.parse(text, { pdoc: true });
> console.log(yield Promise.map(pdoc.filterTemplates(), Parsoid.toWikitext));
[ '{{foo|bar={{baz|{{spam}}}}}}',
  '{{baz|{{spam}}}}',
  '{{spam}}' ]

You can also pass { recursive: false } to filterTemplates() and explore templates manually. This is possible because the get method on a PTemplate object returns an object containing further PNodeLists:

> var text = "{{foo|this {{includes a|template}}}}";
> var pdoc = yield Parsoid.parse(text, { pdoc: true });
> var templates = pdoc.filterTemplates({ recursive: false });
> console.log(yield Promise.map(templates, Parsoid.toWikitext));
[ '{{foo|this {{includes a|template}}}}' ]
> var foo = templates[0];
> console.log(yield foo.get(1).value.toWikitext());
this {{includes a|template}}
> var more = foo.get(1).value.filterTemplates();
> console.log(yield Promise.map(more, Parsoid.toWikitext));
[ '{{includes a|template}}' ]
> console.log(yield more[0].get(1).value.toWikitext());
template

Templates can be easily modified to add, remove, or alter params. Templates also have a nameMatches() method for comparing template names, which takes care of capitalization and white space:

> var text = "{{cleanup}} '''Foo''' is a [[bar]]. {{uncategorized}}";
> var pdoc = yield Parsoid.parse(text, { pdoc: true });
> pdoc.filterTemplates().forEach(function(template) {
...    if (template.nameMatches('Cleanup') && !template.has('date')) {
...        template.add('date', 'July 2012');
...    }
...    if (template.nameMatches('uncategorized')) {
...        template.name = 'bar-stub';
...    }
... });
> console.log(yield pdoc.toWikitext());
{{cleanup|date = July 2012}} '''Foo''' is a [[bar]]. {{bar-stub}}

At any time you can convert the pdoc into HTML conforming to the MediaWiki DOM spec (by referencing the document property) or into wikitext (by invoking toWikitext(), which returns a Promise for the wikitext string). This allows you to save the page using either standard API methods or the RESTBase API (once T101501 is resolved).

For more tips, check out PNodeList's full method list and the list of PNode subclasses.

License

Copyright (c) 2011-2015 Wikimedia Foundation and others.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.