Git Product home page Git Product logo

node-address-rfc2821's Introduction

Build Status Coverage Status

address-rfc2821

Parser for RFC-821/RFC-2821/RFC-5321 (envelope) format email addresses (Mailbox and Path).

This module parses email addresses from the SMTP envelope. These are the portions immediately following the SMTP verbs MAIL FROM: and RCPT TO:. RFC-5321 email addesses look like this:

<>             // null
<Postmaster>
<[email protected]>
<[email protected]>
<[email protected]>
<"quoted string"@example.com>
[email protected]

To parse email addresses contained in the message headers (To: From: BCC, CC), look instead at an RFC 2822/5322 parser such as address-rfc2822 or email-addresses.

Installation

npm install address-rfc2821

Usage

const Address = require('address-rfc2821').Address;

const parsed = new Address('<[email protected]>');

Address Object

The Address object is an interface to reading email addresses passed in at SMTP time. It parses all the formats in RFC-2821 and 2822, as well as UTF8 email addresses according to the RFCs 5890, 5891 and 5892 providing the domain in punycode when encountered It also supports correctly escaping email addresses.

API

  • new Address (user, host)

Create a new address object for user@host

  • new Address (email)

Creates a new address object by parsing the email address. Will throw an exception if the address cannot be parsed.

  • address.user

Access the local part of the email address

  • address.host

Access the domain part of the email address, decoded if necessary to punycode

  • address.original_host

Access the domain part of the email address, unencoded and case preserved

  • address.format(use_punycode=false)

Provides the email address in the appropriate <user@host> format. And deals correctly with the null sender and local names.

If use_punycode = true, uses address.host instead of address.original_host.

  • address.toString()

Same as format().

  • address.address(newval=null, use_punycode=false)

Provides the email address in 'user@host' format.

If use_punycode = true, uses address.host instead of address.original_host.

License

This module is MIT licensed.

node-address-rfc2821's People

Contributors

analogic avatar baudehlo avatar gene-hightower avatar greenkeeper[bot] avatar msimerson avatar sent avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

node-address-rfc2821's Issues

nearley output is incompatible with node.js < 11

nearly produces output that uses array.flat() which doesn't exist in node < 11. Nearly installs just fine, it compiles the grammar.js file, but then when Haraka calls it it crashes because .flat doesn't exist.

I see a couple options:

  1. revert the 1.x branch of this module to the pre-nearley version. Then publish this module with those changes as a 2.x branch. When Haraka drops support for node 10 in a few months, we can update to the newer major version.
  2. drop node.js 10.x support now.
  3. add Array.prototype.flat polyfill to the grammar.js file
  4. ???

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 mocha is breaking the build ๐Ÿšจ

The devDependency mocha was updated from 7.0.0 to 7.0.1.

๐Ÿšจ View failing branch.

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

mocha 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 failed (Details).
  • โœ… continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes for v7.0.1

7.0.1 / 2020-01-25

๐Ÿ› Fixes

  • #4165: Fix exception when skipping tests programmatically (@juergba)
  • #4153: Restore backwards compatibility for reporterOptions (@holm)
  • #4150: Fix recovery of an open test upon uncaught exception (@juergba)
  • #4147: Fix regression of leaking uncaught exception handler (@juergba)

๐Ÿ“– Documentation

๐Ÿ”ฉ Other

Commits

The new version differs by 9 commits.

  • d0f04e9 Release v7.0.1
  • 2277958 update CHANGELOG for v7.0.1 [ci skip]
  • 0be3f78 Fix exception when skipping tests programmatically (#4165)
  • c0f1d14 uncaughtException: fix recovery when current test is still running (#4150)
  • 9c10ada Fix backwards compability break for reporterOptions
  • a24683f Throw a descriptive error when a non-function is given to a runnable (#4133)
  • 579fd09 update copyright & trademark notices per OJSF; closes #4145
  • 0e1ccbb Fix leaking global 'uncaughtException' handler (#4147)
  • 7d78f20 Broken links in docs (#4140)

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 ๐Ÿšจ

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.

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).

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 ๐ŸŒด

Cannot find module `./grammar.js`

Was unsure where to put this. I opened another issue in the core Haraka plugin repo:
#32

Describe the bug
Import error with new grammar.js compiled file.

Expected behavior
Haraka should run.

Observed behavior

internal/modules/cjs/loader.js:969
  throw err;
  ^
Error: Cannot find module './grammar.js'
Require stack:
- /usr/local/lib/node_modules/Haraka/node_modules/address-rfc2821/index.js
- /usr/local/lib/node_modules/Haraka/connection.js
- /usr/local/lib/node_modules/Haraka/logger.js
- /usr/local/lib/node_modules/Haraka/haraka.js
- /usr/local/lib/node_modules/Haraka/bin/haraka
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15)
    at Function.Module._load (internal/modules/cjs/loader.js:842:27)
    at Module.require (internal/modules/cjs/loader.js:1026:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/Haraka/node_modules/address-rfc2821/index.js:6:46)
    at Module._compile (internal/modules/cjs/loader.js:1138:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
    at Module.load (internal/modules/cjs/loader.js:986:32)
    at Function.Module._load (internal/modules/cjs/loader.js:879:14)
    at Module.require (internal/modules/cjs/loader.js:1026:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/usr/local/lib/node_modules/Haraka/node_modules/address-rfc2821/index.js',
    '/usr/local/lib/node_modules/Haraka/connection.js',
    '/usr/local/lib/node_modules/Haraka/logger.js',
    '/usr/local/lib/node_modules/Haraka/haraka.js',
    '/usr/local/lib/node_modules/Haraka/bin/haraka'
  ]
}

Steps To Reproduce
Install a fresh copy of Haraka via npm. Run haraka -i test and then haraka -c test

System Info:

Haraka Haraka.js โ€” Version: 2.8.26
Node v12.18.2
OS Linux instance-1 5.8.0-1011-gcp haraka/Haraka#11-Ubuntu SMP Thu Nov 5 16:51:36 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
openssl OpenSSL 1.1.1f 31 Mar 2020

Additional context
Looks to be related to this commit and the use of this new grammar.js library.

`npm install` does not run postinstall

Describe the bug
npm install does not run postinstall script on some versions of NPM. As a result, grammar.js is not generated and Haraka complains that the file does not exist.

Steps To Reproduce
Run npm install in the root directory of this repo as root on some versions of NPM (mine is 6.14.4).

System Info:

Haraka Haraka.js โ€” Version: 2.8.26
Node v10.19.0
OS Linux mail-production-1 5.4.0-1029-oracle #31-Ubuntu SMP Wed Oct 21 13:50:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
openssl OpenSSL 1.1.1f 31 Mar 2020

NPM version: 6.14.4

Additional Context:
One way that we could resolve this is just by modifying the instructions to have the user manually run npm run postinstall. I'm unsure how we could modify this though to run postinstall scripts when installing Haraka from npm.

Address parser not RFC 5321 compliant

system info

Linux (Fedora 31)

Haraka from git repo, head.

Expected behaviour

Tried a few addresses from the Wikipedia page https://en.wikipedia.org/wiki/Email_address#Examples

Observed behaviour

Tried some addresses from the "valid" list that failed, specifically quoted strings in the local part seem to be a problem area.

$ telnet localhost 2225
Trying ::1...
Connected to localhost.
Escape character is '^]'.
220 digilicious.com ESMTP Haraka/2.8.25 ready
EHLO digilicious.com
250-digilicious.com Hello localhost.localdomain [::1]Haraka is at your service.
250-PIPELINING
250-8BITMIME
250-SMTPUTF8
250 SIZE 0
MAIL FROM:<" "@DiGiLiCious.com>
501-Command parsing failed
501 Error: Invalid local part in address: " "@DiGiLiCious.com

Also, some of the invalid address seem to go just fine:

MAIL FROM:<just"not"[email protected]>
250 sender <"just"not"right"@DiGiLiCious.com> OK

Should have failed, I think.

Also:

MAIL FROM:<this is"not\[email protected]>
250 sender <"this\ is"not\allowed"@DiGiLiCious.com> OK

...and other, I think you get the idea.

Other areas that seemed to be a problem where UTF-8 in the domain part of an address. With SMTPUTF8 support that should work.

Steps to reproduce

Just telnet to Haraka and speak SMTP.

I guess my question is, are you guys open to using a parser that follows the RFC-5321 mailbox syntax?

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 ๐ŸŒด

An in-range update of mocha is breaking the build ๐Ÿšจ

The devDependency mocha was updated from 7.0.1 to 7.1.0.

๐Ÿšจ View failing branch.

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

mocha 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 failed (Details).
  • โœ… continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes for v7.1.0

7.1.0 / 2020-02-26

๐ŸŽ‰ Enhancements

#4038: Add Node.js native ESM support (@giltayar)

Mocha supports writing your test files as ES modules:

  • Node.js only v12.11.0 and above
  • Node.js below v13.2.0, you must set --experimental-modules option
  • current limitations: please check our documentation
  • for programmatic usage: see API: loadFilesAsync()

Note: Node.JS native ECMAScript Modules implementation has status: Stability: 1 - Experimental

๐Ÿ› Fixes

๐Ÿ“– Documentation

๐Ÿ”ฉ Other

Commits

The new version differs by 10 commits.

  • 09b948b Release v7.1.0
  • d43092e update CHANGELOG for v7.1.0 [ci skip]
  • 57be455 Add support for Node.JS native ES modules (#4038)
  • a995e33 Fix: programmatic API cannot access retried test objects (#4181)
  • ac12f2c Browser: fix 'allowUncaught' handling (#4174)
  • 2ff1cb2 uncaughtException: refactor, move and add tests
  • b431609 docs: update browser options
  • 883ae4b ESLint: use 'const' instead of 'let'
  • 2a1b637 Upgrade: ESLint v6.8 (#4138)
  • dbba276 Manage author list in AUTHORS instead of package.json (#4058)

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 mocha is breaking the build ๐Ÿšจ

The devDependency mocha was updated from 6.1.4 to 6.2.0.

๐Ÿšจ View failing branch.

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

mocha 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.2.0

6.2.0 / 2019-07-18

๐ŸŽ‰ Enhancements

๐Ÿ› Fixes

๐Ÿ“– Documentation

๐Ÿ” Coverage

๐Ÿ”ฉ Other

Commits

The new version differs by 39 commits.

  • bd47776 Release v6.2.0
  • cc595af update CHANGELOG.md for v6.2.0 [ci skip]
  • 59d70ee fix: remove duplicate line-height property (#3957)
  • f77cac4 fix: do not redeclare variable (#3956)
  • 6201e42 Hide stacktrace when cli args are missing (#3963)
  • 88f45d5 Don't re-initialize grep option on watch re-run (#3960)
  • 5d4dd98 Fix No Files error when file is passed via --files (#3942)
  • 15b96af Collect test files later (#3953)
  • ccee5f1 Base reporter store ref to console.log (#3725)
  • 47318a7 update @mocha/contributors to v1.0.4 (#3944)
  • c903147 More, improved integration tests for watching (#3929)
  • e341ea4 Update CI config files to use Node-12.x (#3919)
  • 3064d25 update @mocha/docdash to v2.1.1 (#3945)
  • 9ea45e7 do not fork if no node flags present (#3827)
  • d02a096 modify Mocha constructor to accept options.global or options.globals (#3914)

There are 39 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-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.

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 ๐ŸŒด

Generating parser in postinstall triggering nearley installation

The postinstall script in package.json:

"postinstall": "npx -p nearley nearleyc grammar.ne -o grammar.js",

Is triggering a nearley package install in our systems during the bootstrap phase of our repo. I'm not exactly sure why, as the nearley package should already exist. This only appeared after upgrading Haraka to the latest version. For us this breaks things (probably because of locking down npm installs).

I thought I would log this as an issue as others may have run into it.

If you add the --no-install flag (or simply --no for npm >= 7, though --no-install still works), the local nearley should be used.

Alternatively, postinstall scripts are generally best avoided unless absolutely required. The grammar generation could be moved into a prepack or pretest script. Looking at other examples of nearley it looks like it still needs to be a dependency, but generating the js at build time seems acceptable.

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 ๐ŸŒด

An in-range update of mocha is breaking the build ๐Ÿšจ

Version 3.4.0 of mocha just got published.

Branch Build failing ๐Ÿšจ
Dependency mocha
Current Version 3.3.0
Type devDependency

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

As mocha 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/travis-ci/push The Travis CI build failed Details

Release Notes v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

  • allowUncaught added to commandline as --allow-uncaught (and bugfixed)
  • warning-related Node flags

๐ŸŽ‰ Enhancements

๐Ÿ› Fixes

๐Ÿ”ฉ Other

Commits

The new version differs by 9 commits0.

  • 7554b31 Add Changelog for v3.4.0
  • 9f7f7ed Add --trace-warnings flag
  • 92561c8 Add --no-warnings flag
  • ceee976 lint test/integration/fixtures/simple-reporter.js
  • dcfc094 Revert "use semistandard directly"
  • 93392dd no special case for macOS running Karma locally
  • 4d1d91d --allow-uncaught cli option
  • fb1e083 fix allowUncaught in browser
  • 4ed3fc5 Add license report and scan status

false

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 mocha is breaking the build ๐Ÿšจ

The devDependency mocha was updated from 6.0.2 to 6.1.0.

๐Ÿšจ View failing branch.

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

mocha 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.1.0

6.1.0 / 2019-04-07

๐Ÿ”’ Security Fixes

  • #3845: Update dependency "js-yaml" to v3.13.0 per npm security advisory (@plroebuck)

๐ŸŽ‰ Enhancements

  • #3766: Make reporter constructor support optional options parameter (@plroebuck)
  • #3760: Add support for config files with .jsonc extension (@sstephant)

๐Ÿ“  Deprecations

These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:

๐Ÿ› Fixes

  • #3829: Use cwd-relative pathname to load config file (@plroebuck)
  • #3745: Fix async calls of this.skip() in "before each" hooks (@juergba)
  • #3669: Enable --allow-uncaught for uncaught exceptions thrown inside hooks (@givanse)

and some regressions:

๐Ÿ“– Documentation

๐Ÿ”ฉ Other

  • #3830: Replace dependency "findup-sync" with "find-up" for faster startup (@cspotcode)
  • #3799: Update devDependencies to fix many npm vulnerabilities (@XhmikosR)
Commits

The new version differs by 28 commits.

  • f4fc95a Release v6.1.0
  • bd29dbd update CHANGELOG for v6.1.0 [ci skip]
  • aaf2b72 Use cwd-relative pathname to load config file (#3829)
  • b079d24 upgrade deps as per npm audit fix; closes #3854
  • e87c689 Deprecate this.skip() for "after all" hooks (#3719)
  • 81cfa90 Copy Suite property "root" when cloning; closes #3847 (#3848)
  • 8aa2fc4 Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)
  • 586bf78 Update JS-YAML to address security issue (#3845)
  • d1024a3 Update doc examples "tests.html" (#3811)
  • 1d570e0 Delete "/docs/example/chai.js"
  • ade8b90 runner.js: "self.test" undefined in Browser (#3835)
  • 0098147 Replace findup-sync with find-up for faster startup (#3830)
  • d5ba121 Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)
  • a3089ad update package-lock
  • 75430ec Upgrade yargs-parser dependency to avoid loading 2 copies of yargs

There are 28 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 ๐ŸŒด

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.