As per title. "Ma" is the 10th most common surname in China.

Also noticed "Tuan" is treated as the Malay salutation, but it's also a very popular Vietnamese first name, I'd argue more commonly so.

If you pass just the first name, lastName is set to undefined. Should this return empty string instead of undefined?

var name = human.parseName('John');
// {firstName: "John", fullName: "John", lastName: undefined}

https://tonicdev.com/sajin/56282fac4826d80d005e1ca4

Hi!

Thanks for everything you did so far!
I think it would be great if someone can just copy and paste name + address (eg. Clipboard).
Right now it doesn't work and you need to copy paste twice or do some extra separation work outside the plugin.

Thanks!

Do you consider valuable and meaningful feature for parsing name out of an email address? E.g. [email protected] => Mila Votradovec.

I am willing to contribute, but want to discuss the idea first.

Hey, when clicking this link:

It seems to be broken:

The brits still use these...

A Queen's Counsel (post-nominal QC), or King's Counsel (post-nominal KC) during the reign of a king, is a lawyer (usually a barrister or advocate) who is appointed by the monarch to be one of "Her Majesty's Counsel learned in the law."

https://en.wikipedia.org/wiki/Queen%27s_Counsel

When parseName for a salutation and last name only, it is returning first name:

var
  human = require("humanparser"),
  attrs = human.parseName("Ms. Smith")
;
console.log(attrs);

actual:

{ 
    saluation: 'Mr',
    firstName: 'Smith',
    lastName: '',
    fullName: 'Mr Smith'
}

expected:

{ 
    saluation: 'Mr',
    firstName: '',
    lastName: 'Smith',
    fullName: 'Mr Smith'
}

van den is not treated like van der

humanparser.parseName('Caroline van den Brul')
{ firstName: 'Caroline',
  lastName: 'Brul',
  middleName: 'van den',
  fullName: 'Caroline van den Brul' }

humanparser.parseName('Caroline van der Brul')
{ firstName: 'Caroline',
  lastName: 'van der Brul',
  fullName: 'Caroline van der Brul' }

PR inbound :-)

Hi,
It seems IE11 does not support the includes, entries method.

Working on a PR

P/R coming soon, I discovered this issue earlier when I was trying to parse a name that had multiple middle names.

So a name like Tommy A B Lee would come back with a middleName: 'B A' when it should have had middleName: 'A B'

p.s. Thanks for a very helpful module.

Example: the name "Jan van der Steen" is sometimes abbreviated in Dutch as "Jan vd Steen". Currently, this will parse "vd" as a middle name, but it should be part of the last name: "vd Steen". I propose adding "vd" to the list of compounds.

replace var with const.

It's currently undocumented.

Returns "lastname": ""Hearst Jr."

This format of writing names is not in the tests, and unfortunately breaks the parsing ability. This is the format of names for one of the databases I inherited recently.

I tried to split the last name based off of spaces, but of course that then breaks multiple word last names like "Van De Car"

PR inbound :-)

//produces the following output

{
salu T ation: 'Mr.',
firstName: 'William',
suffix: 'III',
lastName: 'Hearst',
middleName: 'R.',
fullName: 'Mr. William R. Hearst, III'
}

"Doe, John" is not parsing correctly
parses to:
{ firstName: 'Doe,', lastName: 'John', fullName: 'Doe, John' }
should parse to:
{ firstName: 'John', lastName: 'Doe', fullName: 'John Doe' }

If a nickname is present, it is read as part of the middle name.

humanparser.parseName('George Herman “Babe” Ruth')

{ firstName: 'George',
  lastName: 'Ruth',
  middleName: 'Herman “Babe”',
  fullName: 'George Herman “Babe” Ruth' }

Since v1.8.0 there is a bug that completely breaks my feathersjs app. Just adding the following anywhere makes all request to the app throw the error.

const human = require('humanparser');

error: argument name is invalid

This is a pretty good parser but it needs some more exhaustive tests:

{
    name: 'Mr. Hearst',
    result: {
        salutation: 'Mr.',
        firstName: '',
        middleName: '',
        lastName: 'Hearst',
        suffix: '',
        fullName: 'Mr. Hearst'
    }
},

The line f06d306#diff-168726dbe96b3ce427e7fedce31bb0bcR3

breaks projects.
By modifying Array.prototype, you will cause a bunch of undesirable behaviours, like:

for (var index in []) {
  console.log(index);
}

outputs

undefined
diff

Please, don't modify Array.prototype.

When I parse "Mike Jones", Middle Name should be blank. But it returns:
firstName="Mike",
middleName="Mike",
lastName="Jones"

Thank you for the library.
Would you be willing to add TypeScript typings? Or at least review them (I can add them).

http://www.typescriptlang.org/docs/handbook/declaration-files/introduction.html Here's a reference on what it is and how works.

If you want an example of how it is done, https://github.com/DefinitelyTyped/DefinitelyTyped/ is a good source of knowledge