haraka / node-address-rfc2822 Goto Github PK

View Code? Open in Web Editor NEW

50.0 9.0 16.0 82 KB

Parser for RFC2822 (Header) format email addresses

Home Page: https://www.npmjs.com/package/address-rfc2822

JavaScript 100.00%

email parser rfc2822 headers

node-address-rfc2822's Introduction

address-rfc2822

Parser for RFC 2822 & 5322 (Header) format email addresses.

This module parses RFC 2822 headers containing addresses such as From, To, CC, and BCC headers.

It is almost a direct port of the perl module Mail::Address and I'm grateful to the original authors of that module for the clean code and the tests.

Installation

npm install address-rfc2822

Usage

const addrparser = require('address-rfc2822')

const addresses = addrparser.parse('Matt Sergeant <[email protected]>')
const address = addresses[0]

console.log(`Email address: ${address.address}`) // [email protected]
console.log(`Email name: ${address.name()}`)     // Matt Sergeant
console.log(`Reformatted: ${address.format()}`)  // Matt Sergeant <[email protected]>
console.log(`User part: ${address.user()}`)      // helpme+npm
console.log(`Host part: ${address.host()}`)      // gmail.com

More Info

License

This module is MIT licensed.

node-address-rfc2822's People

Contributors

Stargazers

Watchers

Forkers

mkandalf markstos cityofboston dr1276 umdez chesnokovilya osm 0xflotus isabella232 ambroseus dwali h2atecnologia chungcf2006 kesselb seanpm2001 0xgoerlimainnet

node-address-rfc2822's Issues

An in-range update of eslint is breaking the build 🚨

Version 4.0.0 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	3.19.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v4.0.0

4aefb49 Chore: avoid using deprecated rules on ESLint codebase (#8708) (Teddy Katz)
389feba Chore: upgrade deps. (#8684) (薛定谔的猫)
3da7b5e Fix: Semi-Style only check for comments when tokens exist (fixes #8696) (#8697) (Reyad Attiyat)
3cfe9ee Fix: Add space between async and param on fix (fixes #8682) (#8693) (Reyad Attiyat)
c702858 Chore: enable no-multiple-empty-lines on ESLint codebase (#8694) (Teddy Katz)
34c4020 Update: Add support for parens on left side for-loops (fixes: #8393) (#8679) (Victor Hom)
735cd09 Docs: Correct the comment in an example for no-mixed-requires (#8686) (Fangzhou Li)
026f048 Chore: remove dead code from prefer-const (#8683) (Teddy Katz)

Commits

The new version differs by 119 commits.

c61194f 4.0.0
821a1e6 Build: changelog update for 4.0.0
4aefb49 Chore: avoid using deprecated rules on ESLint codebase (#8708)
389feba Chore: upgrade deps. (#8684)
3da7b5e Fix: Semi-Style only check for comments when tokens exist (fixes #8696) (#8697)
3cfe9ee Fix: Add space between async and param on fix (fixes #8682) (#8693)
c702858 Chore: enable no-multiple-empty-lines on ESLint codebase (#8694)
34c4020 Update: Add support for parens on left side for-loops (fixes: #8393) (#8679)
735cd09 Docs: Correct the comment in an example for no-mixed-requires (#8686)
026f048 Chore: remove dead code from prefer-const (#8683)
a8e1c1c 4.0.0-rc.0
1768dc0 Build: changelog update for 4.0.0-rc.0
0058b0f Update: add --fix to no-debugger (#8660)
b4daa22 Docs: Note to --fix option for strict rule (#8680)
4df33e7 Chore: check for root:true in project sooner (fixes #8561) (#8638)

There are 119 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

document what happens when parsing fails

Thanks for this module.

I tried parsing the values of undefined, null and "" (empty string). The first two threw exceptions, while the later returned an undefined or null object, such that I couldn't call address.address on the result.

I would prefer that parsing simple fail in the cases of undefined and null. However failure is expressed, it should be documented.

Text between square brackets generates a "No Results" error

Some addresses I met contain text between brackets and this module generates an error. A simple example:

> const addrparser = require('address-rfc2822');
> const addresses = addrparser.parse("Matt Sergeant [hello] <[email protected]>");
Uncaught Error: No results
    at Object.parse (/home/project/node_modules/address-rfc2822/index.js:32:22)

In section 3.2.1 of the RFC2822, these brackets are described with No special semantics are attached to these tokens. They are simply single characters.
I don't know how the text between brackets should be handled but an error seems inappropriate.

Handle escaped quotes

The following email is currently not valid but should be in my opinion.

"Test \" Test" <[email protected]>

Better handling non-latin names

Hey @haraka

Thanks for the module!

By the way I found a little issue with non-latin names.

I suppose the culprit is here - https://github.com/haraka/node-address-rfc2822/blob/master/index.js#L258

When it tries to parse non-latin names it makes them all lowercase, because \b doesn't match begging non-ASCII names.

F.e. try to parse "Имя Фамилия" <[email protected]>

Would you like to accept a PR? I could make it immediately, but not sure if project is still alive so it will be merged at sometime.

current repo URL is 404

package up a new release with updated metadata.

An in-range update of eslint-plugin-haraka is breaking the build 🚨

The devDependency eslint-plugin-haraka was updated from `1.0.11` to `1.0.12`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-haraka is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 1 commits.

3fcc7ee V1.0.12 (#21)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-haraka is breaking the build 🚨

Version 1.0.6 of eslint-plugin-haraka just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-haraka
Current Version	1.0.5
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-haraka is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits.

99d1051 bump version
0906a4a reduce no-useless-escape to warn only
968b392 SublimeLint breaks if you don't use full path (#4)
d6ab389 add node env to .eslintrc
c04dd99 add .eslintrc.json
508f6b7 version bump 1.0.5

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-haraka is breaking the build 🚨

The devDependency eslint-plugin-haraka was updated from `1.0.9` to `1.0.10`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

The devDependency eslint was updated from `5.16.0` to `6.0.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v6.0.0

81aa06b Upgrade: [email protected] (#11869) (Teddy Katz)
5f022bc Fix: no-else-return autofix produces name collisions (fixes #11069) (#11867) (Milos Djermanovic)
ded9548 Fix: multiline-comment-style incorrect message (#11864) (golopot)
cad074d Docs: Add JSHint W047 compat to no-floating-decimal (#11861) (Timo Tijhof)
41f6304 Upgrade: sinon (#11855) (Toru Nagashima)
167ce87 Chore: remove unuseable profile command (#11854) (Toru Nagashima)
c844c6f Fix: max-len properly ignore trailing comments (fixes #11838) (#11841) (ZYSzys)
1b5661a Fix: no-var should not fix variables named 'let' (fixes #11830) (#11832) (Milos Djermanovic)
4d75956 Build: CI with Azure Pipelines (#11845) (Toru Nagashima)
1db3462 Chore: rm superfluous argument & fix perf-multifiles-targets (#11834) (薛定谔的猫)
c57a4a4 Upgrade: @babel/polyfill => core-js v3 (#11833) (薛定谔的猫)
65faa04 Docs: Clarify prefer-destructuring array/object difference (fixes #9970) (#11851) (Oliver Sieweke)
81c3823 Fix: require-atomic-updates reports parameters (fixes #11723) (#11774) (Toru Nagashima)
aef8ea1 Sponsors: Sync README with website (ESLint Jenkins)

Commits

The new version differs by 134 commits.

a7985a6 6.0.0
be74dd9 Build: changelog update for 6.0.0
81aa06b Upgrade: [email protected] (#11869)
5f022bc Fix: no-else-return autofix produces name collisions (fixes #11069) (#11867)
ded9548 Fix: multiline-comment-style incorrect message (#11864)
cad074d Docs: Add JSHint W047 compat to no-floating-decimal (#11861)
41f6304 Upgrade: sinon (#11855)
167ce87 Chore: remove unuseable profile command (#11854)
c844c6f Fix: max-len properly ignore trailing comments (fixes #11838) (#11841)
1b5661a Fix: no-var should not fix variables named 'let' (fixes #11830) (#11832)
4d75956 Build: CI with Azure Pipelines (#11845)
1db3462 Chore: rm superfluous argument & fix perf-multifiles-targets (#11834)
c57a4a4 Upgrade: @babel/polyfill => core-js v3 (#11833)
65faa04 Docs: Clarify prefer-destructuring array/object difference (fixes #9970) (#11851)
81c3823 Fix: require-atomic-updates reports parameters (fixes #11723) (#11774)

There are 134 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Parsing failed with HTAB?

Hi,
I'm using the lib with haraka 2.8.23.
Normally we use the headers.get_decoded for further processing.
Now we found some mails where the from headersfield is empty.

Searching the logfiles and the originalmail source we found that maybe the htab is a problem in email parsing.

this is in the mailsource:

this is the log message:

decoding of base64 and utf8 seems to work, but parsing not.
I think the mail source is allowed by rfc, as CFWS.

address-rfc2822: modernize & standardize

An in-range update of nearley is breaking the build 🚨

Version 2.7.12 of nearley just got published.

Branch	Build failing 🚨
Dependency	nearley
Current Version	2.7.11
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As nearley is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 4 commits .

f4810da 2.7.12
3b41576 fix leo bug, #159
1e94283 rfc5545-rrule
047e2e7 another tutorial, linked in readme

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Can not parse address like "[email protected] <[email protected]>"

This module works great.
But recently I got some emails including addresses like "[email protected] <[email protected]>", and can not be parsed.

> const emailParser = require('address-rfc2822');
> emailParser.parse("[email protected] <[email protected]>")
Error: No results
    at evalCommandPromise.then (packages/shell-server/shell-server.js:249:21)
    at runBound (domain.js:314:12)
    at bound (domain.js:301:14)
    at defaultEval (repl.js:240:29)
    at ContextifyScript.Script.runInThisContext (vm.js:50:33)
    at repl:1:-49
    at Object.parse (/xxxx/node_modules/address-rfc2822/index.js:20:22)

An in-range update of eslint is breaking the build 🚨

Version 5.0.0 of eslint was just published.

Branch	Build failing 🚨
Dependency	`[eslint](https://github.com/eslint/eslint)`
Current Version	4.19.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v5.0.0

Release blogpost

Migration guide

0feedfd New: Added max-lines-per-function rule (fixes #9842) (#10188) (peteward44)
daefbdb Upgrade: eslint-scope and espree to 4.0.0 (refs #10458) (#10500) (Brandon Mills)
077358b Docs: no-process-exit: recommend process.exitCode (#10478) (Andres Kalle)
f93d6ff Fix: do not fail on unknown operators from custom parsers (fixes #10475) (#10476) (Rubén Norte)
05343fd Fix: add parens for yield statement (fixes #10432) (#10468) (Pig Fang)
d477c5e Fix: check destructuring for "no-shadow-restricted-names" (fixes #10467) (#10470) (Pig Fang)
7a7580b Update: Add considerPropertyDescriptor option to func-name-matching (#9078) (Dieter Luypaert)
e0a0418 Fix: crash on optional catch binding (#10429) (Toru Nagashima)
de4dba9 Docs: styling team members (#10460) (薛定谔的猫)
5e453a3 Docs: display team members in tables. (#10433) (薛定谔的猫)
b1895eb Docs: Restore intentional spelling mistake (#10459) (Wilfred Hughes)

Commits

The new version differs by 148 commits.

36ced0a 5.0.0
5fd5632 Build: changelog update for 5.0.0
0feedfd New: Added max-lines-per-function rule (fixes #9842) (#10188)
daefbdb Upgrade: eslint-scope and espree to 4.0.0 (refs #10458) (#10500)
077358b Docs: no-process-exit: recommend process.exitCode (#10478)
f93d6ff Fix: do not fail on unknown operators from custom parsers (fixes #10475) (#10476)
05343fd Fix: add parens for yield statement (fixes #10432) (#10468)
d477c5e Fix: check destructuring for "no-shadow-restricted-names" (fixes #10467) (#10470)
7a7580b Update: Add considerPropertyDescriptor option to func-name-matching (#9078)
e0a0418 Fix: crash on optional catch binding (#10429)
de4dba9 Docs: styling team members (#10460)
5e453a3 Docs: display team members in tables. (#10433)
b1895eb Docs: Restore intentional spelling mistake (#10459)
a9da57d 5.0.0-rc.0
3ac3df6 Build: changelog update for 5.0.0-rc.0

There are 148 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

Version 4.7.0 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	4.6.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v4.7.0

787b78b Upgrade: Espree v3.5.1 (fixes #9153) (#9314) (Brandon Mills)
1488b51 Update: run rules after node.parent is already set (fixes #9122) (#9283) (Teddy Katz)
4431d68 Docs: fix wrong config in max-len example. (#9309) (薛定谔的猫)
7d24dde Docs: Fix code snippet to refer to the correct option (#9313) (Ruben Tytgat)
12388d4 �Chore: rewrite parseListConfig for a small perf gain. (#9300) (薛定谔的猫)
ce1f084 Update: fix MemberExpression handling in no-extra-parens (fixes #9156) (jackyho112)
0c720a3 Update: allow autofixing when using processors (fixes #7510) (#9090) (Teddy Katz)
838df76 Chore: upgrade deps. (#9289) (薛定谔的猫)
f12def6 Update: indent flatTernary option to handle return (fixes #9285) (#9296) (Teddy Katz)
e220687 Fix: remove autofix for var undef inits (fixes #9231) (#9288) (Victor Hom)
002e199 Docs: fix no-restricted-globals wrong config. (#9305) (薛定谔的猫)
fcfe91a Docs: fix wrong config in id-length example. (#9303) (薛定谔的猫)
2731f94 Update: make newline-per-chained-call fixable (#9149) (João Granado)
61f1093 Chore: avoid monkeypatching Linter instances in RuleTester (#9276) (Teddy Katz)
28929cb Chore: remove Linter#reset (refs #9161) (#9268) (Teddy Katz)
abc8634 Build: re-run browserify when generating site (#9275) (Teddy Katz)
7685fed Fix: IIFE and arrow functions in no-invalid-this (fixes #9126) (#9258) (Toru Nagashima)
2b1eba2 Chore: enable eslint-plugin/no-deprecated-context-methods (#9279) (Teddy Katz)
981f933 Fix: reuse the AST of source code object in verify (#9256) (Toru Nagashima)
cd698ba Docs: move RuleTester documentation to Node.js API page (#9273) (Teddy Katz)
4ae7ad3 Docs: fix inaccuracy in npm run perf description (#9274) (Teddy Katz)
cad45bd Docs: improve documentation for rule contexts (#9272) (Teddy Katz)
3b0c6fd Chore: remove extraneous linter properties (refs #9161) (#9267) (Teddy Katz)
c3231b3 Docs: Fix typo in array-bracket-newline.md (#9269) (宋文强)
51132d6 Fix: Formatters keep trailing '.' if preceded by a space (fixes #9154) (#9247) (i-ron-y)
88d5d4d Chore: remove undocumented Linter#markVariableAsUsed method (refs #9161) (#9266) (Teddy Katz)
09414cf Chore: remove internal Linter#getDeclaredVariables method (refs #9161) (#9264) (Teddy Katz)
f31f59d Chore: prefer smaller scope for variables in codebase (#9265) (Teddy Katz)
3693e4e Chore: remove undocumented Linter#getScope method (#9253) (Teddy Katz)
5d7eb81 Chore: refactor config hash caching in CLIEngine (#9260) (Teddy Katz)
1a76c4d Chore: remove SourceCode passthroughs from Linter.prototype (refs #9161) (#9263) (Teddy Katz)
40ae27b Chore: avoid relying on Linter#getScope/markVariableAsUsed in tests (#9252) (Teddy Katz)
b383d81 Chore: make executeOnFile a pure function in CLIEngine (#9262) (Teddy Katz)
5e0e579 Chore: avoid internal SourceCode methods in Linter tests (refs #9161) (#9223) (Teddy Katz)
adab827 Chore: remove unused eslint-disable comment (#9251) (Teddy Katz)
31e4ec8 Chore: use consistent names for apply-disable-directives in tests (#9246) (Teddy Katz)
7ba46e6 Fix: shebang error in eslint-disable-new-line; add tests (fixes #9238) (#9240) (i-ron-y)
8f6546c Chore: remove undocumented defaults() method (refs #9161) (#9237) (Teddy Katz)
82d8b73 Docs: Fix error in example code for sort-imports (fixes #8734) (#9245) (i-ron-y)
a32ec36 Update: refactor eslint-disable comment processing (#9216) (Teddy Katz)
583f0b8 Chore: avoid using globals in CLIEngine tests (#9242) (Teddy Katz)
c8bf687 Chore: upgrade [email protected] (#9234) (薛定谔的猫)
3c41a05 Chore: always normalize rules to new API in rules.js (#9236) (Teddy Katz)
c5f4227 Chore: move logic for handling missing rules to rules.js (#9235) (Teddy Katz)
bf1e344 Chore: create report translators lazily (#9221) (Teddy Katz)
2eedc1f Chore: remove currentFilename prop from Linter instances (refs #9161) (#9219) (Teddy Katz)
5566e94 Docs: Replace misleading CLA links (#9133) (#9232) (i-ron-y)
c991630 Chore: remove ConfigOps.normalize in favor of ConfigOps.getRuleSeverity (#9224) (Teddy Katz)
171962a Chore: remove internal Linter#getAncestors helper (refs #9161) (#9222) (Teddy Katz)
a567499 Chore: avoid storing list of problems on Linter instance (refs #9161) (#9214) (Teddy Katz)
ed6d088 Chore: avoid relying on undocumented Linter#getFilename API in tests (#9218) (Teddy Katz)

Commits

The new version differs by 55 commits.

439e8e6 4.7.0
2ec62f9 Build: changelog update for 4.7.0
787b78b Upgrade: Espree v3.5.1 (fixes #9153) (#9314)
1488b51 Update: run rules after node.parent is already set (fixes #9122) (#9283)
4431d68 Docs: fix wrong config in max-len example. (#9309)
9d1df92 Chore: Revert "avoid handling Rules instances in config-validator" (#9295)
7d24dde Docs: Fix code snippet to refer to the correct option (#9313)
12388d4 �Chore: rewrite parseListConfig for a small perf gain. (#9300)
ce1f084 Update: fix MemberExpression handling in no-extra-parens (fixes #9156)
0c720a3 Update: allow autofixing when using processors (fixes #7510) (#9090)
838df76 Chore: upgrade deps. (#9289)
f12def6 Update: indent flatTernary option to handle return (fixes #9285) (#9296)
e220687 Fix: remove autofix for var undef inits (fixes #9231) (#9288)
002e199 Docs: fix no-restricted-globals wrong config. (#9305)
fcfe91a Docs: fix wrong config in id-length example. (#9303)

There are 55 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-haraka is breaking the build 🚨

Version 1.0.8 of eslint-plugin-haraka just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-haraka
Current Version	1.0.7
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 4 commits.

a5b007d import lint updates from haraka/.eslintrc (#13)
1d563c2 Repo badges (#11)
e1d8fe0 docs(readme): add Greenkeeper badge (#10)
a4947f1 add appveyor.yml (#9)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

haraka / node-address-rfc2822 Goto Github PK

node-address-rfc2822's Introduction

address-rfc2822

Installation

Usage

More Info

License

node-address-rfc2822's People

Contributors

Stargazers

Watchers

Forkers

node-address-rfc2822's Issues

Version 4.0.0 of eslint just got published.

The devDependency eslint-plugin-haraka was updated from 1.0.11 to 1.0.12.

Version 1.0.6 of eslint-plugin-haraka just got published.

The devDependency eslint-plugin-haraka was updated from 1.0.9 to 1.0.10.

The devDependency eslint was updated from 5.16.0 to 6.0.0.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

Version 2.7.12 of nearley just got published.

Version 5.0.0 of eslint was just published.

Version 4.7.0 of eslint just got published.

Version 1.0.8 of eslint-plugin-haraka just got published.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency eslint-plugin-haraka was updated from `1.0.11` to `1.0.12`.

The devDependency eslint-plugin-haraka was updated from `1.0.9` to `1.0.10`.

The devDependency eslint was updated from `5.16.0` to `6.0.0`.