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

@enmaso/node-ner

v1.0.5

Published

Lightweight Nodejs Stanford NER package

Downloads

3

Readme

node-ner

Lightweight Nodejs Stanford NER Project module

Requirements

Pre-installation

Stanford NER needs to be running as a tcp server, default is 8080. Copy server.sh to same directory as stanford-ner project.

/stanford-ner-2017-06-09
|  /classifiers
|  /lib
|  build.xml
|  stanford-ner.jar
|  ...
|  server.sh

Run the server

sudo ./server.sh 8080

If you change the TCP port from 8080, you need to make sure you define the port in your project method. The parse method defaults to port 8080.

Installation

npm install --save @enmaso/node-ner

Usage

const ner = require('@enmaso/node-ner')

let file = 'path/to/file.extension'
ner.parse(file, (tags) => {
  console.log(tags)
})

Returns JSON object. If you use a port other than 8080 for the NERServer, you will need to pass the port in with your parse method

ner.parse(file, 8080, (tags) => {
  console.log(tags)
})

Kill Stanford NERServer

$ ps -A |grep java
$ kill -9 PID

PID will be the first number of the server.sh process

Contributions

Always looking for testing and bug reporting.

License

See License GPL-3.0