Coder Social home page Coder Social logo

ammobin-client's People

Contributors

dependabot[bot] avatar greenkeeper[bot] avatar imgbot[bot] avatar letaylor622 avatar louim avatar nexus-uw avatar snyk-bot avatar

Stargazers

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

Watchers

 avatar  avatar  avatar

ammobin-client's Issues

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

Version 1.81.0 of snyk was just published.

Branch Build failing 🚨
Dependency snyk
Current Version 1.80.0
Type devDependency

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

snyk 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/codeship Build failed Details

Commits

The new version differs by 1 commits.

  • 8db3a39 feat: bump nuget plugin to 1.6.1

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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

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

The dependency nuxt was updated from 2.2.0 to 2.3.0.

🚨 View failing branch.

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

nuxt 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/codeship: 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 apollo-client is breaking the build 🚨

There have been updates to the apollo-client monorepo:

    • The dependency apollo-boost was updated from 0.4.0 to 0.4.1.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the apollo-client group definition.

apollo-client 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
  • now/package.json: has failed
  • now: Deployment has failed (Details).
  • continuous-integration/codeship: Build succeeded (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 now is breaking the build 🚨

Version 9.2.2 of now was just published.

Branch Build failing 🚨
Dependency now
Current Version 9.2.1
Type devDependency

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

now 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/codeship Build failed Details

Release Notes 9.2.2

Patches

  • Temporarily disable progress bar: f95cbe0
  • Show an even better message: 7c891ac
Commits

The new version differs by 3 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 🌴

Filter by Store

Having the ability to filter by store would be a nice benefit. Sometimes I know shipping costs are high so I want to compare only the local options. Right now I have to expand a bunch of the cheapest ones to see if its in a local store.

An in-range update of @nuxtjs/pwa is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.0.7 of @nuxtjs/pwa was just published.

Branch Build failing 🚨
Dependency @nuxtjs/pwa
Current Version 2.0.6
Type dependency

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

@nuxtjs/pwa 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/codeship 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 nuxt is breaking the build 🚨

Version 1.2.0 of nuxt was just published.

Branch Build failing 🚨
Dependency nuxt
Current Version 1.1.1
Type dependency

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

nuxt 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/codeship Build failed Details

Commits

The new version differs by 60 commits.

  • 78494da nuxt: Bump to v1.2.0
  • a713f9a npm: Upgrade dependencies
  • 3235b03 Merge pull request #2633 from homerjam/fix-route-transitions-example
  • 6d71770 Merge pull request #2687 from NicoPennec/dev
  • 1ab4be4 fix: Handle redirect in middleware, fix #542 and #2665
  • 5f50d40 Merge pull request #2673 from clarkdo/static_route
  • 6425fb3 Merge pull request #2679 from clarkdo/multiple_components
  • ae00499 fix: avoid warning of too big vendor
  • fdc07a3 perf: chunks size limit
  • 94bb029 fix: multiple components in one route
  • fcf99b1 Merge pull request #2674 from clarkdo/head_noscript
  • d0e011b Update meta.js
  • 8b634c2 feat: add noscript in head
  • 00f98c1 fix: Fix error undefined on plugins errors
  • 82c4c7e refactor: resolve exact route prior to index

There are 60 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 @nuxtjs/axios is breaking the build 🚨

The dependency @nuxtjs/axios was updated from 5.5.3 to 5.5.4.

🚨 View failing branch.

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

@nuxtjs/axios 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/codeship: Build in progress (Details).
  • now/package.json: has failed
  • now: Deployment has failed (Details).

Release Notes for v5.5.4

Bug Fixes

  • ignore content-length header (41ff27a)
Commits

The new version differs by 2 commits.

  • c4e73d0 chore(release): 5.5.4
  • 41ff27a fix: ignore content-length header

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

The devDependency husky was updated from 2.3.0 to 2.4.0.

🚨 View failing branch.

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

husky 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
  • now/package.json: has failed
  • now: Deployment has failed (Details).
  • continuous-integration/codeship: Build succeeded (Details).

Commits

The new version differs by 19 commits.

There are 19 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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

An in-range update of @typescript-eslint/eslint-plugin is breaking the build 🚨

The devDependency @typescript-eslint/eslint-plugin was updated from 1.9.0 to 1.10.0.

🚨 View failing branch.

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

@typescript-eslint/eslint-plugin 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/codeship: Build in progress (Details).
  • now/package.json: has failed
  • now: Deployment has 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 apollo-client is breaking the build 🚨

There have been updates to the apollo-client monorepo:

    • The dependency apollo-boost was updated from 0.4.0 to 0.4.1.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the apollo-client group definition.

apollo-client 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
  • now/package.json: has failed
  • now: Deployment has failed (Details).
  • continuous-integration/codeship: Build succeeded (Details).

Commits

The new version differs by 42 commits.

  • 4db0a73 chore: Publish
  • fe4c2ff Update root package-lock.json after adding lodash.isequal.
  • 21cfe5d Update CHANGELOG.md with new patch versions.
  • 2593f8f Reimplement custom isEqual apollo-utilities function using lodash.isequal (#4915)
  • 5048b1b Compile ESM bundle to CJS using Babel instead of Rollup. (#4911)
  • 4bd8237 docs: fix typo in react-apollo-migration.md (#4893)
  • b927458 Merge pull request #4907 from apollographql/renovate/typescript-3.x
  • b5af622 Fix TypeScript errors in tests/writeToStore.ts.
  • bd0bd82 chore(deps): update dependency typescript to v3.5.1
  • f7ecafa chore(deps): update dependency tslint to v5.17.0
  • 28cb683 chore(deps): update dependency rollup-plugin-node-resolve to v5.0.1
  • 3103fe3 chore(deps): update dependency uglify-js to v3.6.0
  • f3c5695 chore(deps): update dependency flow-bin to v0.100.0
  • c3097a7 chore(deps): update dependency @types/react to v16.8.19
  • da84c58 chore(deps): update dependency @types/node to v12.0.4

There are 42 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 apollo-client is breaking the build 🚨

There have been updates to the apollo-client monorepo:

    • The dependency apollo-boost was updated from 0.4.0 to 0.4.1.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the apollo-client group definition.

apollo-client 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
  • now/package.json: has failed
  • now: Deployment has failed (Details).
  • continuous-integration/codeship: Build succeeded (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 @nuxt/typescript is breaking the build 🚨

The devDependency @nuxt/typescript was updated from 2.7.1 to 2.8.0.

🚨 View failing branch.

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

@nuxt/typescript 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/codeship: Build in progress (Details).
  • now/package.json: has failed
  • now: Deployment has failed (Details).

Release Notes for v2.8.0

😎 Developer Experience

  • #5770 Add a group for SSR logs to avoid polluting the browser console
  • #5810 Fancier browser logs with consola

nuxt-ssr-logs-2

  • #5820, #5832, #5834 Show build indicator in the browser when rebuilding code:

nuxt-hmr-indicator

  • #5753 Watch for pages/ creation when default page displayed
  • #5812 Only listen for file changes for supported extensions
  • #5753 Re-use the same port when randomly assigned when restarting in dev mode

🐛 Bug Fixes

  • vue-renderer
    • #5807 Add User-Agent‍ to Vary header in modern server mode
    • #5764 Safe format SSR logs
  • server
    • #5793 Preserve random port when restarting
    • Return listener when calling listen
  • builder
    • #5753 Watch for pages/ creation when default page displayed
    • #2812 Only listen for file changes for supported extensions
  • generator
    • #5791 Minify spa fallback
  • types
    • #5785 Add type definition for functional babel.presets
  • vue-app
    • #5757 Reuse page component with watchQuery
    • #5746 Remove trailing slash in vue-router non-strict mode
    • #5752 Don't attach catch handler to already loaded component
    • #5824 fixPrepatch in-out transition fix (issue #5797)
  • utils
    • #5754 Handle serializeFunction edge case

🚀 Features

  • vue-renderer
    • #5745 Add render.injectScripts option
    • #5784 Support render.ssrLog for controlling SSR logs

💅 Refactors

  • core
    • #5796 Use require.resolve instead of Module internals
  • builder
    • #5792 Pass nuxt options to template as nuxtOptions
  • vue-app
    • #5770 Add a group for SSR logs
    • #5826 simplify mount error log
  • general
    • #5748 Small readability improvements

📝 Examples

  • auth-jwt
    • #5775 Use named store export to prevent warning
  • typescript
    • #5742 Add missing ts-node dependency

🏡 Chore

  • ci
    • #5802 Upload test report to CircleCI and Azure
    • Add flags for codecov
  • general
    • Remove unused dependency cross-env
    • Add FUNDING.md
    • Improve links in readme

♻️ Tests

  • general
    • #5790 Add unit tests for core/resolver.js
    • #5782 Remove duplicate unit tests in packages/core/test/resolver

⚓ Dependency upgrades

💖 Thanks to

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 @nuxtjs/axios is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 5.2.0 of @nuxtjs/axios was just published.

Branch Build failing 🚨
Dependency @nuxtjs/axios
Current Version 5.1.1
Type dependency

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

@nuxtjs/axios 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/codeship Build failed Details

Commits

The new version differs by 5 commits.

  • c944b00 chore(release): 5.2.0
  • 4ec3b5d feat: consola integration
  • 5367bd5 Create ISSUE_TEMPLATE.md
  • 27aa4bd docs(setup): add module.exports in nuxt.config.js (#120)
  • a90236e fix(progress): onProgress when currentRequests is zero (#118)

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 🌴

add shipping estimator

  • should assume canpar ground shipping
  • need to get all vendor postal addresses
  • would require user to enter postal address (or province or city) (or use user's IP to guess server side)
  • only for those items with unit cost
  • need a guesstimate of how heavy everything is
  • would display shipping along side price

An in-range update of apollo-client is breaking the build 🚨

There have been updates to the apollo-client monorepo:

    • The dependency apollo-boost was updated from 0.4.0 to 0.4.1.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the apollo-client group definition.

apollo-client 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
  • now/package.json: has failed
  • now: Deployment has failed (Details).
  • continuous-integration/codeship: Build succeeded (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 browserslist is breaking the build 🚨

The dependency browserslist was updated from 4.6.1 to 4.6.2.

🚨 View failing branch.

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

browserslist 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/codeship: Build in progress (Details).
  • now/package.json: has failed
  • now: Deployment has 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 snyk is breaking the build 🚨

Version 1.61.1 of snyk was just published.

Branch Build failing 🚨
Dependency snyk
Current Version 1.61.0
Type devDependency

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

snyk 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

Release Notes v1.61.1

<a name"1.61.1">

1.61.1 (2017-12-19)

Bug Fixes

  • make sure that we set the homedir of the user correctly (9848e8b7)
Commits

The new version differs by 2 commits.

  • 9848e8b fix: make sure that we set the homedir of the user correctly
  • 1c53d53 test: remove Node 8 from Appveyor

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

The dependency boxen was updated from 4.0.0 to 4.1.0.

🚨 View failing branch.

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

boxen 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/codeship: Build in progress (Details).
  • now/package.json: has failed
  • now: Deployment has failed (Details).

Release Notes for v4.1.0

Maintenance release to update dependencies. No user-facing changes.

v4.0.0...v4.1.0

Commits

The new version differs by 3 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 🌴

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

Version 1.75.0 of snyk was just published.

Branch Build failing 🚨
Dependency snyk
Current Version 1.74.0
Type devDependency

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

snyk 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/codeship Build failed Details

Release Notes v1.75.0

<a name"1.75.0">

1.75.0 (2018-04-29)

Bug Fixes

  • code styling issues detected by lgtm (c6f467e2)
  • pin snyk-policy version (aa6040e7)

Features

  • bail out on unsupported nodejs runtime versions (9bc11d13)
Commits

The new version differs by 3 commits.

  • c6f467e fix: code styling issues detected by lgtm
  • 9bc11d1 feat: bail out on unsupported nodejs runtime versions
  • aa6040e fix: pin snyk-policy version

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

The devDependency surge was updated from 0.21.0 to 0.21.1.

🚨 View failing branch.

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

surge 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/codeship: Build in progress (Details).
  • now: Now is deploying your app (Details).
  • now/package.json: has failed

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 🌴

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

The dependency nuxt was updated from 2.7.1 to 2.8.0.

🚨 View failing branch.

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

nuxt 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/codeship: Build in progress (Details).
  • now/package.json: has failed
  • now: Deployment has failed (Details).

Release Notes for v2.8.0

😎 Developer Experience

  • #5770 Add a group for SSR logs to avoid polluting the browser console
  • #5810 Fancier browser logs with consola

nuxt-ssr-logs-2

  • #5820, #5832, #5834 Show build indicator in the browser when rebuilding code:

nuxt-hmr-indicator

  • #5753 Watch for pages/ creation when default page displayed
  • #5812 Only listen for file changes for supported extensions
  • #5753 Re-use the same port when randomly assigned when restarting in dev mode

🐛 Bug Fixes

  • vue-renderer
    • #5807 Add User-Agent‍ to Vary header in modern server mode
    • #5764 Safe format SSR logs
  • server
    • #5793 Preserve random port when restarting
    • Return listener when calling listen
  • builder
    • #5753 Watch for pages/ creation when default page displayed
    • #2812 Only listen for file changes for supported extensions
  • generator
    • #5791 Minify spa fallback
  • types
    • #5785 Add type definition for functional babel.presets
  • vue-app
    • #5757 Reuse page component with watchQuery
    • #5746 Remove trailing slash in vue-router non-strict mode
    • #5752 Don't attach catch handler to already loaded component
    • #5824 fixPrepatch in-out transition fix (issue #5797)
  • utils
    • #5754 Handle serializeFunction edge case

🚀 Features

  • vue-renderer
    • #5745 Add render.injectScripts option
    • #5784 Support render.ssrLog for controlling SSR logs

💅 Refactors

  • core
    • #5796 Use require.resolve instead of Module internals
  • builder
    • #5792 Pass nuxt options to template as nuxtOptions
  • vue-app
    • #5770 Add a group for SSR logs
    • #5826 simplify mount error log
  • general
    • #5748 Small readability improvements

📝 Examples

  • auth-jwt
    • #5775 Use named store export to prevent warning
  • typescript
    • #5742 Add missing ts-node dependency

🏡 Chore

  • ci
    • #5802 Upload test report to CircleCI and Azure
    • Add flags for codecov
  • general
    • Remove unused dependency cross-env
    • Add FUNDING.md
    • Improve links in readme

♻️ Tests

  • general
    • #5790 Add unit tests for core/resolver.js
    • #5782 Remove duplicate unit tests in packages/core/test/resolver

⚓ Dependency upgrades

💖 Thanks to

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:

  • Replaced the old Node.js version in your .nvmrc with the new one

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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

An in-range update of es6-promise is breaking the build 🚨

The dependency es6-promise was updated from 4.2.6 to 4.2.7.

🚨 View failing branch.

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

es6-promise 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
  • now/package.json: has failed
  • now: Deployment has failed (Details).
  • continuous-integration/codeship: Build succeeded (Details).

Commits

The new version differs by 5 commits.

  • a2bcc62 release v4.2.7 🎉
  • 37e6fe3 update changelog
  • 21e755a Merge pull request #345 from stefanpenner/remove-try-catch-hacks
  • e33ab9d Remove try/catch avoidance hacks as they are no longer needed (as per @bmeurer’s guidance)
  • 95e8fbf remove getThen

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

Version 1.41.0 of snyk just got published.

Branch Build failing 🚨
Dependency snyk
Current Version 1.40.4
Type devDependency

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

As snyk 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 could not complete due to an error Details

Release Notes v1.41.0

<a name"1.41.0">

1.41.0 (2017-09-21)

Bug Fixes

  • ignore the vuln in tough-cookie (67749906)

Features

  • migrate from request to needle (09570c90)
Commits

The new version differs by 4 commits.

  • 195bdb2 test: temporarily disable Travis Node 0.12 tests
  • 7f82b6d chore: prune .snyk policy file
  • 09570c9 feat: migrate from request to needle
  • 6774990 fix: ignore the vuln in tough-cookie

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 @nuxt/typescript is breaking the build 🚨

The devDependency @nuxt/typescript was updated from 2.8.0 to 2.8.1.

🚨 View failing branch.

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

@nuxt/typescript 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
  • now/package.json: has failed
  • now: Deployment has failed (Details).
  • continuous-integration/codeship: Build succeeded (Details).

Release Notes for v2.8.1

🐛 Bug Fixes

  • vue-renderer
    • #5867 Fix exception on property access of undefined object
    • #5863 Prevent "can't set headers after they are sent" error in modern server mode
  • vue-app
    • #5864 Reduce consola direct access and don't override browser console.log
  • cli
    • #5865 Don't mutate options export to prevent ESM regression with nuxt.config in mixed (cjs + esm) mode (TIP: never mix them as is non-standard and may be unsupported in any future version)

💅 Refactors

  • typescript
    • #5854 Prepare for external typescript support

💖 Thanks to

  • Rafał Chłodnicki (@rchl)
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 @nuxtjs/axios is breaking the build 🚨

The dependency @nuxtjs/axios was updated from 5.5.2 to 5.5.3.

🚨 View failing branch.

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

@nuxtjs/axios 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/codeship: Build in progress (Details).
  • now: Now is deploying your app (Details).
  • now/package.json: has failed

Commits

The new version differs by 4 commits.

  • e58983d chore(release): 5.5.3
  • ee8f999 fix: bump axios to ^0.19.0
  • c7cbf4e chore(deps): update dependency consola to ^2.7.1 (#252)
  • f56c4fb chore(deps): bump webpack-bundle-analyzer from 3.1.0 to 3.3.2 (#251)

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

Version 1.53.0 of snyk was just published.

Branch Build failing 🚨
Dependency snyk
Current Version 1.52.1
Type devDependency

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

snyk 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

Release Notes v1.53.0

<a name"1.53.0">

1.53.0 (2017-12-01)

Bug Fixes

  • bump snyk policy to latest release (633ecd12)

Features

  • display the settings used when conducting a test (91e083a2)
  • upgrade snyk-policy to support disregardIfFixable (bb828a94)
Commits

The new version differs by 3 commits.

  • 633ecd1 fix: bump snyk policy to latest release
  • 91e083a feat: display the settings used when conducting a test
  • bb828a9 feat: upgrade snyk-policy to support disregardIfFixable

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

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 11.0.7 of now was just published.

Branch Build failing 🚨
Dependency now
Current Version 11.0.6
Type devDependency

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

now 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/codeship Build failed Details

Release Notes 11.0.7

Patches

  • Validate now.json before parsing it: #1239
  • Remove unused dependencies: #1258
  • Re-added dependencies required for download: #1259
  • Replaced the update checker: #1275
  • Don't render update message on non-TTY: #1281

Credits

Huge thanks to @sreeramjayan and @javivelasco for helping!

Commits

The new version differs by 6 commits.

  • 26b11b8 11.0.7
  • e1f8c75 Don't render update message on non-TTY (#1281)
  • e1c5af5 Replaced the update checker (#1275)
  • 01363a5 Re-added dependencies required for download (#1259)
  • 0f1471f Remove unused dependencies (#1258)
  • 0e7ce49 Validate now.json before parsing it (#1239)

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

The devDependency snyk was updated from 1.170.0 to 1.171.0.

🚨 View failing branch.

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

snyk 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/codeship: Build in progress (Details).
  • now/package.json: has failed
  • now: Deployment has failed (Details).

Release Notes for v1.171.0

1.171.0 (2019-06-02)

Features

  • add branch and pkg name to monitor analytics (b91d2ae)
Commits

The new version differs by 6 commits.

  • 305ac09 Merge pull request #543 from snyk/feat/add_monitor_branch_pname_analytics
  • b91d2ae feat: add branch and pkg name to monitor analytics
  • 464b784 Merge pull request #544 from snyk/chore/delete-docker-promo
  • d82df40 chore: delete expired docker promo
  • 3d66ee6 Merge pull request #534 from snyk/chore/refactor-errors
  • 76b0565 chore: refactor snyk missing api token

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

Version 11.1.11 of now was just published.

Branch Build failing 🚨
Dependency now
Current Version 11.1.10
Type devDependency

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

now 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/codeship Build failed Details

Release Notes 11.1.11

Patches

  • Store config on platform & load schema from package: #1349
Commits

The new version differs by 2 commits.

  • 48a4907 11.1.11
  • b96b7fc Store config on platform & load schema from package (#1349)

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

Version 1.95.1 of snyk was just published.

Branch Build failing 🚨
Dependency snyk
Current Version 1.95.0
Type devDependency

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

snyk 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/codeship: Build failed (Details).

Release Notes v1.95.1

1.95.1 (2018-09-09)

Bug Fixes

  • bump mvn,gradle and sbt plugins for better error handling (34dc3a6)
Commits

The new version differs by 2 commits.

  • f650729 Merge pull request #213 from snyk/fix/bump-plugins
  • 34dc3a6 fix: bump mvn,gradle and sbt plugins for better error handling

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

The dependency nuxt was updated from 2.8.0 to 2.8.1.

🚨 View failing branch.

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

nuxt 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
  • now/package.json: has failed
  • now: Deployment has failed (Details).
  • continuous-integration/codeship: Build succeeded (Details).

Release Notes for v2.8.1

🐛 Bug Fixes

  • vue-renderer
    • #5867 Fix exception on property access of undefined object
    • #5863 Prevent "can't set headers after they are sent" error in modern server mode
  • vue-app
    • #5864 Reduce consola direct access and don't override browser console.log
  • cli
    • #5865 Don't mutate options export to prevent ESM regression with nuxt.config in mixed (cjs + esm) mode (TIP: never mix them as is non-standard and may be unsupported in any future version)

💅 Refactors

  • typescript
    • #5854 Prepare for external typescript support

💖 Thanks to

  • Rafał Chłodnicki (@rchl)
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 snyk is breaking the build 🚨

The devDependency snyk was updated from 1.169.1 to 1.169.2.

🚨 View failing branch.

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

snyk 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/codeship: Build in progress (Details).
  • now/package.json: has failed
  • now: Deployment has failed (Details).

Release Notes for v1.169.2

1.169.2 (2019-05-29)

Bug Fixes

  • remove incorrect Gradle logging (d1bc261)
Commits

The new version differs by 2 commits.

  • 9b9435f Merge pull request #541 from snyk/fix/remove-unnecessary-gradle-logging
  • d1bc261 fix: remove incorrect Gradle logging

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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Take into account sale taxes

It would be great if the site could take into account sale taxes.

How I see it could work:

  • Users are located with their IP, or just select a dropdown with their province.
  • User could opt out of the feature (with a checkbox or the like)
  • Sale taxes would be calculated based on the province the user is and the province the vendor is.

For example, as a Quebec resident, if I choose a Quebec retailer (like Canadian Tire or Sail), it would add Quebec GST 5% and QST (Quebec Sales Tax) 9.975% to the prices. If I choose a retailer from Ontario, it would add only the 5% GST to the prices.

What do you think?

cabelas links are incorrect

ex:
shotgun => http://www.cabelas.ca2-3/4"?utm_source=ammobin.ca
pistol => http://www.cabelas.ca?utm_source=ammobin.ca
rifle => http://www.cabelas.caQtyfunction addToBasket(productId, productInformation) {var event = {};event.customerId = 'cabelasca';event.projectId = 'cabelasca1Production';event.visit = {};event.visit.visitorId = '142882080';event.eventType = 'addToBasket';event.product = {}; event.product.productId = '31118'; event.product.id = '31118'; event.product.sapgenericnumber = '40333';event.visit = {};event.visit.visitorId = '142882080';gbEvent.send(event);}(function() { var ssl = 'https:' == document.location.protocol;var s = document.getElementsByTagName('script')[0]; var gb = document.createElement('script');gb.charset = 'UTF-8';gb.type = 'text/javascript'; gb.async = true; gb.src = (ssl ? 'https://tracker-secure' : 'http://tracker') + '.groupbycloud.com/js/gb-tracker.js'; s.parentNode.insertBefore(gb, s);})();utm_source=ammobin.ca
rimefire => http://www.cabelas.ca/product/70650/winchester-22-lr-bulk-packs?productVariantId=224724utm_source=ammobin.ca

An in-range update of copy-webpack-plugin is breaking the build 🚨

Version 4.2.2 of copy-webpack-plugin was just published.

Branch Build failing 🚨
Dependency copy-webpack-plugin
Current Version 4.2.1
Type dependency

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

copy-webpack-plugin 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 Release v4.2.2

4.2.2 (2017-11-23)

Bug Fixes

  • copying same file to multiple targets (#165) (43a9870)
Commits

The new version differs by 8 commits ahead by 8, behind by 2.

  • 6e81e75 chore(release): 4.2.2
  • 13fe3c8 refactor: use const instead var
  • 19b3a17 chore(package): remove unused dependencies (fs-extra, node-dir)
  • af80033 chore: drop unused deps
  • 7707512 refactor: use const instead var
  • dcddf86 docs: Fixes changelog issue from 4.2.1
  • 7477183 chore(release): 4.2.1
  • 43a9870 fix: copying same file to multiple targets (#165)

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.