vincentbriglia/node-emerchantpay

emerchantpay Parameter Signer library for node backend

node-emerchantpay's Issues

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 prettier is breaking the build 🚨

Version 1.9.0 of prettier was just published.

Branch	Build failing 🚨
Dependency	prettier
Current Version	1.8.2
Type	devDependency

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

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

---

Release Notes

1.9.0: JSX Fragments, EditorConfig and Arrow Parens

This release adds an option for arrow function parens in arguments, support for the new JSX fragment syntax (<>), support for .editorconfig files, and nice additions to our GraphQL and Markdown support.

Highlights

JavaScript

Option to add parens in arrow function arguments (#3324) by @rattrayalex and @suchipi

When printing arrow functions, Prettier omitted parens around the arguments if they weren’t strictly necessary, like so:

// no parens
foo => {};
// parens

(foo: Number) => {};
// parens

({ foo }) => {}
// parens

(foo = 5) => {}

This lead to the most commented thread in our issue tracker. Prettier now has the --arrow-parens option (arrowParens in the config) that can assume two values today:

• "avoid" - (default) preserve the behavior that omits parens when possible
• "always" - always includes parens

JSX fragment syntax (#3237) by @duailibe

Prettier will now recognize and format JSX with the new fragment syntax, like the code below:

function MyComponent() {
  return (
    <>
      <Children1 />
      <Children2 />
      <Children3 />
    </>
  );
}

Fix slow formatting long texts in JSX (#3268, #3273) by @duailibe

We received feedback that formatting a JSX file with a really long text (~1000 lines) was really slow and noticed there was two performance bottlenecks in our fill primitive, which prints text until it reaches the print width and then insert a line break.

Markdown

Add an option to preserve text line breaks (#3340) by @ikatyang

After the release of our Markdown support, we received feedback that breaking text to respect the print width could affect some renderers that could be sensitive to line breaks. In 1.8.2 we released a new option proseWrap: false that would print a paragraph in a single line, and users would rely on the "soft wrapping" feature of editors.

In 1.9 we are releasing a new option proseWrap: "preserve" which will respect the original line breaks of text, and lets the users decide where the text should break.

[WARNING] proseWrap with boolean value is deprecated, use "always", "never" or "preserve" instead.

[BREAKING CHANGE] proseWrap option now defaults to "preserve" as some renderers are linebreak-sensitive.

GraphQL

Support top-level interpolations (#3370) by @lydell

When GraphQL support was released, Prettier did not support interpolation so it would skip formatting if any interpolations were present, because interpolations make formatting very difficult. While that works well for the most part, users of the Apollo Client were missing out on Prettier’s GraphQL support sometimes, because Apollo Client uses interpolation to share fragments between queries. The good news is that only top-level interpolations are allowed, and that was way easier to add support for in Prettier.

In 1.9 we format GraphQL queries with top-level interpolation:

gql`
  query User {
    user(id: "Bob") {
      ...UserDetails
    }
  }

  ${UserDetailsFragment}
`

(Prettier will continue to skip formatting if the interpolation is inside a query or mutation or so.)

Preserve intentional new lines in GraphQL (#3252) by @duailibe

Prettier will now respect intentional line breaks inside GraphQL queries (but limit to 1), where before it would remove them.

query User {
  name
age

}

CSS

Don't lowercase element names and attribute names in selectors (#3317) by @lydell

CSS is mostly case insensitive, so Prettier has been lowercasing stuff for a while to keep things consistent. Turns out we overlooked a detail in the CSS spec. Element and attribute names in selectors depend on the markup language: In HTML they are case insensitive, but in SVG (XML) they are not. Previously Prettier would incorrectly lowercase element and attribute names, but now we don’t anymore.

Configuration

Add EditorConfig support (#3255) by @josephfrazier

It's taken a while, but Prettier will finally respect your .editorconfig file. This includes:

• indent_style
• indent_size/tab_width
• max_line_length

The prettier CLI respects .editorconfig by default, but you can opt out with --no-editorconfig.
However, the API doesn't respect .editorconfig by default, in order to avoid potential editor integration issues (see here for details). To opt in, add editorconfig: true to the prettier.resolveConfig options.

Other changes

JavaScript

Don't break simple elements in JSX (#3250) by @duailibe

Prettier won't break an element with no attributes anymore, keeping elements like <br /> as an unit.

Don't break identifiers inside template literals expressions (#3299) by @duailibe

In the previous release we tried a new strategy of breaking template literals with expressions inside to respect the print width. We've received feedback that for some cases it was actually preferred that it would exceed print width than breaking in multiple lines.

From now on, template literals expressions that contain a single identifier won't break anymore:

const foo = `Hello ${username}. Today is ${month} ${day}. You have ${newMessages} new messages`.

Fix formatting of comment inside arrow function (#3334) by @jackyho112

Fixes an edge case where Prettier was moving comments around breaking tools like Webpack:

const API = {
  loader: () => import('./test' /* webpackChunkName: "test" */),
};
// would get formatted to
const API = {

loader: (/ webpackChunkName: "test" /) => import("./test")

};

Fix printing of comments around decorators and class properties (#3382) by @azz

There was a case where comments between a decorator and a class property were moved to an invalid position.

// Before
class Something {
  @decorator
  static // comment
  property = 1;
}
// After

class Something {

@decorator

// comment

static property = 1;

}

Flow

Do not break on empty type parameters (#3281) by @vjeux

It won't break empty type parameters (foo: Type<>) anymore.

Add support for flow mixins when using babylon (#3391) by @bakkot

We were accidentally dropping flow mixins, this has been fixed, but only for the babylon parser.

// Before
class Foo extends Bar {}
// After

class Foo extends Bar mixins Baz {}

TypeScript

Don't print a trailing comma after object rest spread (#3313) by @duailibe

This was inconsistent with JavaScript and Flow, Prettier won't print a trailing comma in the following cases, when using the TypeScript parser:

const {
  bar,
  baz,
  ...rest
} = foo;

Print parens around type assertions for decorators (#3329) by @azz

We were omitting parens around type assertions inside decorators:

@(bind as ClassDecorator)
class Decorated {}

Markdown

Don't break inlineCode (#3230) by @ikatyang

Prettier won't break text inside inlineCode meaning it will only break of after it.

No extra whitespace between non-CJK and CJK-punctuation and vice-versa (#3244, #3249) by @ikatyang

Fixes cases where Prettier would insert extra whitespace like in the following examples:

扩展运算符（spread ）是三个点（`...`）。
This is an english paragraph with a CJK quote " 中文 ".

Escape all emphasis-like text (#3246) by @ikatyang

Fixes the case where \_\_text\_\_ would be formatted as __text__.

Handle punctuation variants (#3254) by @ikatyang

Prettier now considers not only ASCII punctuation characters but Unicode as well.

Support TOML front matter (#3290) by @ikatyang

We already supported YAML in the front matter of Markdown files and we added the TOML format as well, since some static site generators support it.

+++
date: '2017-10-10T22:49:47.369Z'
title: 'My Post Title'
categories: ['foo', 'bar']
+++
This is the markdown body of my post.

Only indent the first non-list node in checkbox list item (#3297) by @ikatyang

Fixes a bug where it would indent lines after a list when it shouldn't:

* parent list item
 <span class="pl-v">*</span> child list item

* [x] parent task list item
 <span class="pl-v">*</span> [x] child task list item</pre></div>

would become:
* parent list item
* child list item
* [x] parent task list item
  <span class="pl-v">*</span> [x] child task list item</pre></div>

Preserve non-breaking whitespaces (#3327) by @ikatyang
Non-breaking whitespaces are useful to keep words separated by spaces together in the same line (i.e. number and units or multi-word product names). Prettier was wrongfully converting them to regular whitespaces.
Do not break before special prefix (#3347) by @ikatyang
Fixes a bug where Prettier could break text if it went over the print width right before a number followed by . which would be parsed as a numbered list:
She grew up in an isolated village in the 19th century and met her father aged
29. Oh no, why are we in a numbered list now?
Omit semicolon in simple JSX expressions (#3330) by @sapegin
Prettier will omit the semicolon (before and after) inside code samples if it's a simple JSX expression:
No semi:
jsx</span><span class="pl-s1"></span> <span class="pl-s1">&lt;div&gt;Example&lt;/div&gt;</span> <span class="pl-s1"></span><span class="pl-c1">

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 4.1.0 of mocha was just published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	4.0.1
Type	devDependency

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

---

Release Notes

v4.1.0

4.1.0 / 2017-12-28

This is mainly a "housekeeping" release.

Welcome @Bamieh and @xxczaki to the team!

🐛: Fixes

• #2661: progress reporter now accepts reporter options (@canoztokmak)
• #3142: xit in bdd interface now properly returns its Test object (@Bamieh)
• #3075: Diffs now computed eagerly to avoid misinformation when reported (@abrady0)
• #2745: --help will now help you even if you have a mocha.opts (@Zarel)

🎉 Enhancements

• #2514: The --no-diff flag will completely disable diff output (@CapacitorSet)
• #3058: All "setters" in Mocha's API are now also "getters" if called without arguments (@makepanic)

📖 Documentation

• #3170: Optimization and site speed improvements (@Munter)
• #2987: Moved the old site repo into the main repo under docs/ (@boneskull)
• #2896: Add maintainer guide (@boneskull)
• Various fixes and updates (@xxczaki, @maty21, @leedm777)

🔩 Other

• Test improvements and fixes (@eugenet8k, @ngeor, @38elements, @Gerhut, @ScottFreeCode, @boneskull)
• Refactoring and cruft excision (@38elements, @Bamieh, @finnigantime, @boneskull)

Commits

The new version differs by 409 commits.

• 6b9ddc6 Release v4.1.0
• 3c4b116 update CHANGELOG for v4.1.0
• 5be22b2 options.reporterOptions are used for progress reporter
• ea96b18 add .fossaignore [ci skip]
• adc67fd Revert "[ImgBot] optimizes images (#3175)"
• ae3712c [ImgBot] optimizes images (#3175)
• 33db6b1 Use x64 node on appveyor
• 4a6e095 Run appveyor tests on x64 platform. Might enable sharp installation
• 3abed9b Lint netlify-headers script
• 119543e Add preconnect for doubleclick domain that google analytics results in contacting
• bd5109e Remove crossorigin='anonymous' from preconnect hints. Only needed for fonts, xhr and es module loads
• 123ee4f Handle the case where all avatars are already loaded at the time when the script exexecutes
• 64deadc Specific value for inlining htmlimages to guarantee logo is inlined
• 8f1ded4 https urls where possible
• d5a5125 Be explicit about styling of screenshot images

There are 250 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.13.0 of eslint was just published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	4.12.1
Type	devDependency

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

---

Release Notes

v4.13.0

• 256481b Update: update handling of destructuring in camelcase (fixes #8511) (#9468) (Erin)
• d067ae1 Docs: Don’t use undocumented array-style configuration for max-len (#9690) (Jed Fox)
• 1ad3091 Chore: fix test-suite to work with node master (#9688) (Myles Borins)
• cdb1488 Docs: Adds an example with try/catch. (#9672) (Jaap Taal)

Commits

The new version differs by 6 commits.

• 29c3610 4.13.0
• ac331bc Build: changelog update for 4.13.0
• 256481b Update: update handling of destructuring in camelcase (fixes #8511) (#9468)
• d067ae1 Docs: Don’t use undocumented array-style configuration for max-len (#9690)
• 1ad3091 Chore: fix test-suite to work with node master (#9688)
• cdb1488 Docs: Adds an example with try/catch. (#9672)

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 lodash is breaking the build 🚨

Version 4.17.5 of lodash was just published.

Branch	Build failing 🚨
Dependency	lodash
Current Version	4.17.4
Type	dependency

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

lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status 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 prettier is breaking the build 🚨

Version 1.7.1 of prettier just got published.

Branch	Build failing 🚨
Dependency	prettier
Current Version	1.7.0
Type	devDependency

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

As prettier 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

---

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 gulp-eslint is breaking the build 🚨

Version 4.0.1 of gulp-eslint was just published.

Branch	Build failing 🚨
Dependency	gulp-eslint
Current Version	4.0.0
Type	devDependency

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

gulp-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/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 6 commits.

• 1d79ed0 4.0.1
• 8f7e966 replace all HTTP protocols with HTTPS
• b48a04a remove deprecated gulp-util dependency (#213)
• 35eae57 update devDependencies (#207)
• 47bd269 use npx to simplify after_script
• 29dbab5 inherit autofix-related props even if quiet option is enabled

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 gulp-istanbul is breaking the build 🚨

Version 1.1.3 of gulp-istanbul was just published.

Branch	Build failing 🚨
Dependency	gulp-istanbul
Current Version	1.1.2
Type	devDependency

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

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

---

Release Notes

v1.1.3

Fix deprecated gulp-utils usage

Commits

The new version differs by 3 commits.

• 6ea01ce 1.1.3
• 7b74390 replaced deprecated gulp-util and fixed broken test (#129)
• 1e3adcb chore(package): update mocha to version 4.0.0 (#126)

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-prettier is breaking the build 🚨

Version 2.4.0 of eslint-plugin-prettier was just published.

Branch	Build failing 🚨
Dependency	eslint-plugin-prettier
Current Version	2.3.1
Type	devDependency

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

eslint-plugin-prettier 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/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 3 commits.

• a728868 Build: update package.json and changelog for v2.4.0
• e529b60 New: Add 'recommended' configuration (#73)
• 4335b08 Docs: Create ISSUE_TEMPLATE.md

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 debug is breaking the build 🚨

Version 3.2.0 of debug was just published.

Branch	Build failing 🚨
Dependency	debug
Current Version	3.1.0
Type	dependency

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

debug is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes

3.2.0

A long-awaited release to debug is available now: 3.2.0.

Due to the delay in release and the number of changes made (including bumping dependencies in order to mitigate vulnerabilities), it is highly recommended maintainers update to the latest package version and test thoroughly.

---

Minor Changes

• bump vulnerable packages: 853853f
• Fix nwjs support (#569): 207a6a2
• add instance extends feature (#524): e43e5fe
• Add TVMLKit support (#579): 02b9ea9

Patches

• move to XO (closes #397): ba8a424
• clean up builds: 3ca2331
• remove needless command aliases in makefile: 9f4f8f5
• no longer checking for BROWSER=1: 623c08e
• fix tests: 57cde56
• clean up makefile: 62822f1
• fix tests: 833b6f8
• add .editorconfig: 2d2509e
• add yarn-error.log to .gitignore: 7e1d5d9
• add Node.js 10, remove Node.js 4 (#583): 05b0ceb
• Improve usability of Windows notes w/ examples for prompts & npm script (#577): 1ad1e4a
• Drop usage of chrome.storage (or make the storage backend pluggable): 71d2aa7
• Detect 'process' package: 225c66f
• Update ms to 2.1.1 (#539): 22f9932
• Update .npmignore (#527): a5ca7a2
• fix colors with supports-color@5: 285dfe1
• Document enable() (#517): ab5083f
• refactor to make the common code be a setup function (#507): 7116906
• Simplify and improve: da51af8

Credits

Huge thanks to @DanielRuf, @EirikBirkeland, @KyleStay, @Qix-, @abenhamdine, @alexey-pelykh, @DiegoRBaquero, @febbraro, @kwolfy, and @TooTallNate for their help!

Commits

The new version differs by 25 commits.

• dec4b15 3.2.0
• 3ca2331 clean up builds
• 9f4f8f5 remove needless command aliases in makefile
• 623c08e no longer checking for BROWSER=1
• 57cde56 fix tests
• 62822f1 clean up makefile
• 833b6f8 fix tests
• ba8a424 move to XO (closes #397)
• 2d2509e add .editorconfig
• 853853f bump vulnerable packages
• 7e1d5d9 add yarn-error.log to .gitignore
• e43e5fe add instance extends feature (#524)
• 207a6a2 Fix nwjs support (#569)
• 05b0ceb add Node.js 10, remove Node.js 4 (#583)
• 02b9ea9 Add TVMLKit support (#579)

There are 25 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 gulp-debug is breaking the build 🚨

Version 3.2.0 of gulp-debug was just published.

Branch	Build failing 🚨
Dependency	gulp-debug
Current Version	3.1.0
Type	devDependency

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

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

---

Commits

The new version differs by 4 commits.

• 8108fdf 3.2.0
• 26226ca Meta tweaks
• 38b9e67 Drop dependency on deprecated gulp-util (#41)
• 4db5871 Rewrite tests to use AVA

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 sinon is breaking the build 🚨

Version 4.1.3 of sinon was just published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	4.1.2
Type	devDependency

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

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

---

Commits

The new version differs by 12 commits.

• 39b0849 Update docs/changelog.md and set new release id in docs/_config.yml
• 6f9af25 4.1.3
• c6bd1de Update History.md and AUTHORS for new release
• 911c498 Spy passes through calling with new (#1626)
• 271d84a Update external_howtos.yml
• e96ff8c CircleCI Integration (#1479)
• 88e9132 Upgrade type-detect dependency to 4.0.5
• 45c4d57 Move yieldsAsync* documentation to the first yieldsAsync*
• 8c54024 Remove sinon.restore(object|method) from v3.x+ docs
• 9ae6f73 Remove sinon.log from 2.x+ docs
• 0111ed0 Update markdownlinter-cli to official v0.4.0
• 109e7b7 Add markdownlint to dependencies

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 🌴