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

dependency-parser

v1.0.4

Published

Parses sentences into dependency trees.

Downloads

12

Readme

dependency-parser

Parses sentences (in the form of an array of objects representing words) into dependency trees.

Try it out.

A dependency tree maps a sentence to a tree in which each word is a node. Every node is either dependent on another node or the head of another node or both. For example, in the sentence "I guess this is life now.":

  • The noun "I" is a dependent of the verb "guess".
  • The verb "is" is a dependent of the verb "guess".
  • The noun "this" is a dependent of the verb "is".
  • The noun "life" is a dependent of the verb "is".
  • The adverb "now" is a dependent of the verb "is".

Elements in an array passed to the parser should look like this:

{
  "word": "guess",
  "pos": [
    "verb"
  ]
}

Where "pos" is the parts of speech. See node-pos or Wordnik about getting parts of speech for words. Any extra elements in the objects will be preserved in the output, so you can throw in metadata if you feel like it.

Uses generators. Requires Node 4+ or ES6 in the browser.

Installation

npm install dependency-parser

Usage

var DependencyParser = require('dependency-parser');
var flipTreeHeadToChild = require('dependency-parser/flip-tree-head-to-child');
var disambiguatePOS = require('dependency-parser/disambiguate-pos');
var parseGenerator = DependencyParser();

var sentence = [
  {
    "word": "i",
    "pos": [
      "noun"
    ]
  },
  {
    "word": "am",
    "pos": [
      "verb"
    ]
  },
  {
    "word": "a",
    "pos": [
      "indefinite-article"
    ]
  },
  {
    "word": "great",
    "pos": [
      "adjective",
      "noun",
      "adverb"
    ]
  },
  {
    "word": "dog",
    "pos": [
      "noun",
      "adverb",
      "verb-transitive",
      "idiom"
    ]
  }
];

var parseGenerator = DependencyParser();
var disambiguatedSentence = disambiguatePOS(sentence, 'pos');
var parseIterator = parseGenerator(sentence);
var parsed = runIteratorUntilDone(parseIterator);
var childBasedTree = flipTreeHeadToChild(parsed.sentence);

console.log(JSON.stringify(childBasedTree, null, '  '))

function runIteratorUntilDone(iterator) {
  var result;
  do {
    result = iterator.next();
  }
  while (!result.done);

  return result.value;
}

Output:

[
  {
    "word": "am",
    "pos": [
      "verb"
    ],
    "sentencePos": 1,
    "defactoPOS": "verb",
    "children": [
      {
        "word": "i",
        "pos": [
          "noun"
        ],
        "sentencePos": 0,
        "defactoPOS": "noun",
        "directionFromHead": -1
      },
      {
        "word": "dog",
        "pos": [
          "noun"
        ],
        "sentencePos": 4,
        "defactoPOS": "noun",
        "children": [
          {
            "word": "a",
            "pos": [
              "indefinite-article"
            ],
            "sentencePos": 2,
            "defactoPOS": "indefinite-article",
            "directionFromHead": -1
          },
          {
            "word": "great",
            "pos": [
              "adjective"
            ],
            "sentencePos": 3,
            "defactoPOS": "adjective",
            "directionFromHead": -1
          }
        ],
        "directionFromHead": 1
      }
    ]
  }
]

The parse function returns an array of trees. If the sentence is well-formed, it should contain a single tree, but otherwise, there may be multiple trees.

Algorithm

The parsing algorithm is derived from A Fundamental Algorithm for Dependency Parsing (PDF) with a modification for not checking anything that is already a dependency of the word node being evaluated when looking for heads.

Tests

Run tests with make test.

TODO

  • Consider adding dependents to other dependents.
  • If there is already a child with the same directionFromHead, try swapping places with that child, ignoring its de facto POS.
  • Consider quitting when you are about to add a third dependent to a head. At that point, it may be clear that you may never really understand the sentence.

Next test cases:

  • No one wants it but the orphans who aged out of the system.
  • My water heater broke and flooded my basement!
  • Obvious exits are NORTH, SOUTH and DENNIS.

License

The MIT License (MIT)

Copyright (c) 2016 Jim Kang

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.