travi / hapi-vary-accept

hapi pre-response handler to include Accept in the Vary header

hapi-vary-accept

hapi pre-response handler to include Accept in the Vary header

Table of Contents

• Motivation
• Usage
  • Installation
• Contribution
  • Verification

Motivation

Google Chrome caches only the last response for any endpoint, regardless of content-type, which results in rendering json data instead of the rendered page based on the html representation. These values are cached even with the Cache-Control header set to no-cache in order to optimize operations like navigating back or duplicating a tab.

While normally unnecessary because of configuring the headers to prevent caching,including Accept in the Vary header does technically further inform a client that a single endpoint responds with different responses based on the Accept header of the request.

• https://bugs.chromium.org/p/chromium/issues/detail?id=94369
• https://bugs.chromium.org/p/chromium/issues/detail?id=108425
• https://stackoverflow.com/questions/1975416/what-is-the-function-of-the-vary-accept-http-header

Usage

Installation

⚠️ This plugin does not yet support hapi v17

$ npm install hapi-vary-accept --save

Contribution

Verification

$ npm test

hapi-vary-accept's Issues

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (security:openssf-scorecard). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

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

The devDependency rollup was updated from 1.24.0 to 1.25.0.

🚨 View failing branch.

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

rollup 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 for v1.25.0

2019-10-18

Features

• Remove try-catch if there is no side-effect in the try-block (#3166)
• Omit side-effect-free trailing cases in switch-statements (#3166)
• Remove unused labels (#3170)

Bug Fixes

• Do not remove code after labeled statements that contain a throw or return if the label is used (#3170)
• Prevent invalid code when expressions are simplified that do not follow a white-space character (#3173)
• Do not remove continue statements inside switch statements (#3166)
• Prevent trailing empty lines when tree-shaking inside switch statements (#3166)

Pull Requests

• #3166: Better try statement tree shaking (@lukastaegert)
• #3170: Handle optional control flow in labeled statements, remove unused labels (@lukastaegert)
• #3173: Add missing spaces in certain statements and expressions to avoid invalid code (@lukastaegert)

Commits

The new version differs by 5 commits.

• d677eb7 1.25.0
• f307c89 Update changelog
• 91cb8f0 Add missing spaces in certain statements and expressions to avoid invalid code (#3173)
• 121a7f4 Handle optional control flow in labeled statements, remove unused labels (#3170)
• 836a106 Better try statement tree shaking (#3166)

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

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The devDependency rollup was updated from 2.6.1 to 2.7.0.

🚨 View failing branch.

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

rollup 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

• ❌ Travis CI - Branch: The build failed.

---

Release Notes for v2.7.0

2020-04-21

Features

• Add preserveEntrySignatures option to control how exports of entry points are handled (#3498)
• Add preserveSignature flag to this.emitFile to control exports of emitted chunks (#3498)
• Add output.minifyInternalExports option to control if internal exports are minified (#3498)

Pull Requests

• #3498: Add option to configure if entry signatures are preserved (@lukastaegert)

Commits

The new version differs by 4 commits ahead by 4, behind by 1.

• 437934e 2.7.0
• c953270 Update changelog
• 9011204 Add option to configure if entry signatures are preserved (#3498)
• c0c206e Use chokidar as test watcher

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 🌴

only enhance responses that might actually vary based on accept

probably just html/json to start with, but maybe make this configurable so consumers can define what makes sense for them

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

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The devDependency rollup was updated from 2.4.0 to 2.5.0.

🚨 View failing branch.

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

rollup 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

• ❌ Travis CI - Branch: The build failed.

---

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 3.0.9 to 3.1.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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v3.1.0

• Add pre-merge-commit hook (#605)

Commits

The new version differs by 5 commits.

• 436ca18 3.1.0
• 795508d add funding field
• 2b601d2 Add pre-merge-commit (#605)
• 3a844a6 Update README.md
• abcb11a update 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 rollup is breaking the build 🚨

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The devDependency rollup was updated from 2.7.2 to 2.7.3.

🚨 View failing branch.

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

rollup 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

• ❌ Travis CI - Branch: The build failed.

---

Release Notes for v2.7.3

2020-04-27

Bug Fixes

• Do not access __proto__ when running Rollup (#3518)

Pull Requests

• #3518: use acorn-class-fields and acorn-static-class-features from npm (@nitsky)

Commits

The new version differs by 3 commits.

• 8db16bd 2.7.3
• ea6dbc0 Update changelog
• 21705fa use acorn-class-fields and acorn-static-class-features from npm (#3518)

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

The devDependency rollup was updated from 1.14.2 to 1.14.3.

🚨 View failing branch.

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

rollup 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 for v1.14.3

2019-06-06

Bug Fixes

• Generate correct external imports when importing from a directory that would be above the root of the current working directory (#2902)

Pull Requests

• #2902: Use browser relative path algorithm for chunks (@lukastaegert)

Commits

The new version differs by 4 commits.

• c68bd95 1.14.3
• d79aa57 Update changelog
• 7179390 Use browser relative path algorithm for chunks (#2902)
• b1df517 Add funding button

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 🌴

hapi v17 support

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

The devDependency rollup was updated from 1.18.0 to 1.19.0.

🚨 View failing branch.

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

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

• 9af119d 1.19.0
• b3f361c Update changelog
• 456f4d2 Avoid variable from empty module name be empty (#3026)
• 17eaa43 Use id of last module in chunk as name base for auto-generated chunks (#3025)
• 871bfa0 Switch to a code-splitting build and update dependencies (#3020)
• 2443783 Unified file emission api (#2999)

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 🌴

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Base branch does not exist - skipping

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): lock file maintenance (master)

Detected dependencies

github-actions

.github/workflows/node-ci.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/setup-node v4.0.0@8f152de45cc393bb48ce5d89d36b731f54556e65
• codecov/codecov-action v3.1.4@eaaf4bedf32dbdc6b720b63067d99c4d77d6047d

.github/workflows/release.yml

npm

package.json

• @babel/register 7.22.15
• @hapi/hapi 21.3.2
• @travi/any 3.0.2
• @travi/babel-preset 3.0.116
• @travi/eslint-config 5.0.7
• @travi/eslint-config-mocha 1.0.21
• c8 8.0.1
• chai 4.3.10
• commitlint-config-travi 1.4.44
• cross-env 7.0.3
• cz-conventional-changelog 3.3.0
• husky 8.0.3
• mocha 10.2.0
• npm-run-all2 6.1.1
• publint 0.2.6
• remark-cli 12.0.0
• remark-preset-lint-travi 6.0.3
• remark-toc 9.0.0
• rimraf 5.0.5
• rollup 4.9.0
• sinon 17.0.1
• @hapi/hapi ^18.0.0 || ^19.0.0 || ^20.0.0 || ^21.0.0

nvm

.nvmrc

• node 20

---

• Check this box to trigger a request for Renovate to run again on this repository

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

The devDependency rollup was updated from 1.9.2 to 1.9.3.

🚨 View failing branch.

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

rollup 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 for v1.9.3

2019-04-10

Bug Fixes

• Simplify return expressions that are evaluated before the surrounding function is bound (#2803)

Pull Requests

• #2803: Handle out-of-order binding of identifiers to improve tree-shaking (@lukastaegert)

Commits

The new version differs by 3 commits.

• 516a06d 1.9.3
• a5526ea Update changelog
• c3d73ff Handle out-of-order binding of identifiers to improve tree-shaking (#2803)

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 @travi/eslint-config-travi is breaking the build 🚨

The devDependency @travi/eslint-config-travi was updated from 1.8.6 to 1.8.7.

🚨 View failing branch.

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

@travi/eslint-config-travi 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 for v1.8.7

1.8.7 (2019-11-04)

Bug Fixes

• package: update eslint-plugin-cucumber to version 1.4.0 (d6fdfc5)

Commits

The new version differs by 2 commits.

• 67c246e chore(package): update lockfile package-lock.json
• d6fdfc5 fix(package): update eslint-plugin-cucumber to version 1.4.0

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

---

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

---

The devDependency rollup was updated from 2.10.2 to 2.10.3.

🚨 View failing branch.

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

rollup 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

• ❌ Travis CI - Branch: The build failed.

---

Release Notes for v2.10.3

2020-05-18

Bug Fixes

• Validate return value of sourcemapPathTransform option (#3561)

Pull Requests

• #3561: Throw error if sourcemapPathTransform-option does not return a string (@Simonwep)

Commits

The new version differs by 3 commits.

• d91fa24 2.10.3
• 425787f Update changelog
• 9b60cb1 Throw error if sourcemapPathTransform-option does not return a string (#3484) (#3561)

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 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀