jackbearheart/email-addresses

Issues

• fails to parse if the name is an email address

  #67 opened a year ago by 7c
  1

• When name has colon in it, it fails to parse

  #66 opened a year ago by liesislukas
  0

• Question: What do you use to generate the minified code?

  #63 opened 2 years ago by paviad
  0

• Feature Request: Include the parsed value in the returned objects

  #62 opened 3 years ago by dariusj18
  1

• Should 'foo@bar.com' (apostrophes included!) be a valid email address?

  #53 opened 4 years ago by xemlock
  2

• latest version with addressListSeparator not available on npm/yarn ?

  #60 opened 3 years ago by rombat
  1

• Doesn't appear to distinguish extended mailboxes

  #35 opened 7 years ago by Qix-
  5

• REQUEST: Could the parser get the ".com" or ".net" part of the email in an isolated part property/field name?

  #56 opened 4 years ago by carlosalvidrez
  2

• `isValid` method?

  #50 opened 5 years ago by niftylettuce
  4

• Bracketing not supported

  #52 opened 4 years ago by Chrisjow
  2

• support ES module importing

  #43 opened 6 years ago by ojanvafai
  2

• Support load patterns for AMD, node, and the browser

  #5 opened 4 years ago by jackbearheart
  1

• Accept address lists with a trailing comma

  #12 opened 4 years ago by bradvogel
  4

• Allow semicolon separator

  #38 opened 6 years ago by wyckster
  2

• How should I detect ParsedGroup?

  #41 opened 4 years ago by RShergold
  5

• `parseOneAddress` sometimes returns `null`

  #48 opened 4 years ago by garyking
  1

• .git

  #42 opened 6 years ago by xingtongju
  5

• Parser fails when quoted string includes dquotes and comma

  #40 opened 6 years ago by Galienna
  1

• Release v3.0.2?

  #39 opened 6 years ago by bkemper
  2

• Space should be disallowed or at least treated consistently

  #37 opened 7 years ago by kscc25
  1

• Line feed in address string will return null

  #36 opened 7 years ago by lnedry
  1

• Simple option doesn't seem to work

  #34 opened 7 years ago by alexlatchford
  1

• rejectTLD option for input with no domain part produces error

  #33 opened 7 years ago by pretender
  1

• Support for rfc6854

  #28 opened 7 years ago by baudehlo
  2

• Parser starts at the wrong place

  #29 opened 7 years ago by baudehlo
  1

• Properly parse FROM email headers with colon, comma characters

  #13 opened 8 years ago by mccolin
  3

• Build an email address string from `email` and `name` components

  #21 opened 8 years ago by campriceaustin
  3

• Submit to JSDelivr

  #20 opened 8 years ago by bradvogel
  3

• dot at the and of the domain

  #22 opened 8 years ago by derhuerst
  5

• TypeScript definition

  #19 opened 9 years ago by blakeembrey
  2

• Whitespaces in address?

  #15 opened 8 years ago by rajhub
  1

• Handle unicode names?

  #8 opened 10 years ago by bradvogel
  3

• Finding email addresses in arbitrary text

  #16 opened 9 years ago by parshap
  3

• Allow dots in address

  #14 opened 9 years ago by bradvogel
  2

• Address list without commas?

  #11 opened 10 years ago by brainkim
  2

• Submit to Bower

  #10 opened 10 years ago by bradvogel
  2

• Names with periods in them don't resolve

  #9 opened 10 years ago by bradvogel
  1

• Quotes incorrectly left in name

  #6 opened 10 years ago by bradvogel
  3

• Misses an option to allow domains without extension

  #7 opened 10 years ago by vasco3
  2

• Document how to get semantic parts

  #3 opened 10 years ago by kevinoid
  2

• Parsing error on email names

  #2 opened 11 years ago by KyleAMathews
  1