hapijs / hapi.dev

The hapi.dev developer portal

@hapi/hapi.dev

The home of the hapi.dev developer portal.

Running/developing

• First, clone or download the repo and run npm install.

• Next, you need to make an .env file in the root directory.

• Obtain a token from GitHub here and select checked scopes only (only two)

  • repo : Full control of private repositories
    • repo status : Access commit status
    • repo_deployment : Access deployment status
    • public_repo : Access public repositories
    • repo:invite : Access repository invitations

• Copy your GitHub token and place it in your .env file by entering: GITHUB_TOKEN = "YOUR TOKEN"

• Run npm run dev and go to http://localhost:3000 to view the site. The dev server hot loads, which will automatically show your changes without having to restart the server.

• Run npm run static and go to http://localhost:3000 to view the site with the actual resulting /dist folder.

• After you make your changes, simply open a pull request.

Add a translation for the tutorials

In the directory static/lib/tutorials we have some directories with the name of the languages translated, to add a new translation, simply add a new folder in the static/lib/tutorials with your translation. An Example, if you translate the tutorials, to Brazilian Portuguese, you must use the pt_BR as the name of the directory. Inside the directory pt_BR, you need to follow the same struture we use in en_US, with all tutorials separated in markdown files and an index.js file that's export the tutorials and the titles. After finish the translations, you also need add your translation in the index.js file inside static/lib/tutorials.

Plugins

hapijs.com maintains a list of community-created plugins here. If there are any plugins you have created or one you use often that isn't listed please send a pull request. Please note the existing categories, but if your plugin does not fit one feel free to create your own. Please keep the plugins in alphabetical order to be fair to all contributors.

Building the docker image

• npm install (installs dependencies in order to run the generate)
• npm run generate (builds the static dist folder)
• npm run docker-build (creates hapi.dev image with just static content)

This builds a static docker image without any secrets. It relies on the dist folder being created from the npm run generate step.

Deployment process

See DEPLOY.md

hapi.dev's Issues

Only v20.x API docs visible

It seems that all the old versions of the API docs has disappeared from the website. E.g. https://hapi.dev/api/?v=18.4.1 now redirects to https://hapi.dev/api/?v=20.0.0

From the version dropdown menu, only 20.0.0 is available:

Sync up with old hapijs.com site changes

test bug

https://hapi.dev/module/joi/tester

It seems changelog is not updated, latest is for 19.0.1

Context

• node version: 12
• module version: 19.1.x

What are you trying to achieve or the steps to reproduce ?

Where can I see changelog for latest version ?
already checked https://hapi.dev/resources/changelog/ but it has not been updated for. 19.1.1

Website scrolls on its own

Support plan

• is this issue currently blocking your project?: no
• is this issue affecting a production system?: no

Context

• OS: Windows 10 Pro (Build 19041)
• Browser: Chrome 89.0.4389.82 (64-bit)

What are you trying to achieve or the steps to reproduce?

I visit the hapi.dev API reference (https://hapi.dev/api/?v=20.1.0)

What was the result you got?

The site scrolls upward on its own.

What result did you expect?

The site not to scroll on its own ¯_(ツ)_/¯. Right now, it makes me quite anxious—like I'm in a race to finish reading what I'm reading before it scrolls out of view.😅

I'm not sure exactly what conditions trigger the auto-scroll. An easy way is to Ctrl-F a term somewhere further in the docs, then scroll a bit (like in the clip below). Some other times, it happens when I nav between sections from the menu.

20.1.0.API.Reference.-.hapi.dev.-.Google.Chrome.2021-03-11.08-42-58.mp4

Add proper translations for default auth behavior

Context

• node version: n/a
• module version: latest

What are you trying to achieve or the steps to reproduce ?

An issue was raised #459 which was fixed in this MR #460 regarding a mismatch between the documentation and the actual default auth strategy behavior. It was fixed in english but not in the other languages. This is a follow-up of #461.

This was fixed in english and we need to update the tutorial in other languages. Here are the missing translations:

• pt-BR
• ko-KR
• tr-TR
• zh-ZN

Any help is appreciated here since the core team cannot work on these translations. If you want to participate just open a PR and mention this issue without Fixes or Closes keywords and we'll tick the related tasks ourselves.

Thank you.

Joi API Documentation Load Failure in Firefox

Support plan

• which support plan is this issue covered by? (e.g. Community, Core, Plus, or Enterprise): Community
• is this issue currently blocking your project? (yes/no): no
• is this issue affecting a production system? (yes/no): no

Context

• node version: N/A
• module version with issue: hapi.dev 1.0.0
• last module version without issue: Unknown
• environment (e.g. node, browser, native): Browser
• used with (e.g. hapi application, another framework, standalone, ...): Firefox
• any other relevant information: Works in Chrome

What are you trying to achieve or the steps to reproduce?

I am trying to view the joi API Documentation for v15.1.1 in Firefox.

I am able to view the latest version's docs (17.0.2). However, when I go to the page for the joi 15.1.1 docs using the version selector dropdown, the page remains on the documentation for 17.0.2.

What was the result you got?

In the console, I see the following:

SyntaxError: invalid regexp group 8cfc73afe0fd4c233e07.js:1:1
ChunkLoadError: "Loading chunk 17 failed.
(missing: https://hapi.dev/_nuxt/8cfc73afe0fd4c233e07.js)"
    NuxtJS 49
SyntaxError: invalid regexp group 8cfc73afe0fd4c233e07.js:1:1

I cannot reproduce this issue for API docs other than joi.

Support Dark Mode

Support plan

• is this issue currently blocking your project? (yes/no): no
• is this issue affecting a production system? (yes/no): no

Context

• node version: n/a
• module version: n/a
• environment (e.g. node, browser, native): n/a
• used with (e.g. hapi application, another framework, standalone, ...): n/a
• any other relevant information: n/a

What problem are you trying to solve?

Being able to look at Hapi's documentation in a dark room without having your eyes blinded.

Do you have a new or modified API suggestion to solve the problem?

add a dark mode switch toggle ?

Documentation on default auth strategy incorrect?

Context

• node version: 15.14.0
• module version: 20.1.2

What are you trying to achieve or the steps to reproduce ?

I'm building an API where all routes are protected by a token based auth strategy. Now I'm trying to register a /health route, which should be exempt from the authentication for obvious reasons.

According to the documentation, defining the route before setting a default auth strategy should yield the desired behaviour:

Note that any routes added before server.auth.default() is called will not have the default applied to them.

However, with the following code (simplified to the relevant parts), I still get a 401 error when calling the /health endpoint:

const tokenScheme = function () {
    return {
        authenticate: async (request, h) => {
            const authorizationHeader = request.headers.authorization;

            const user = await getUser(authorizationHeader);

            if (user) {
                return h.unauthenticated(
                    Boom.unauthorized('Invalid token')'
                );
            }

            return h.authenticated({
                credentials: {
                    user,
                },
            });
        },
    };
};


server.route({
    method: 'GET',
    path: '/health',
    handler: () => {
        return 'up';
    },
});

server.auth.scheme('token', tokenScheme);
server.auth.strategy('token', 'token');
server.auth.default('token');

server.route({
    method: 'GET',
    path: '/user',
    handler: (request) => {
        return request.auth.credentials.user;
    },
});

Specifying

options: {
    auth: false,
}

on the /health route successfully disables authentication.

I'm unsure whether this is expected behaviour and the documentation is just incorrect, or whether this constitutes a bug. I'm happy to provide a PR for a fix either way, if you can clarify.

Invalid coding convention at 'Getting Started' tutorial

Hi,
I found an invalid coding convention at 'Getting Started' tutorial's 'Adding Routes' section.
There is no whitespace at path:'/',.

Thank you.

Expanding submenu items breaks menu item selection

Support plan

• which support plan is this issue covered by? Community
• is this issue currently blocking your project? no
• is this issue affecting a production system? no

Context

• node version: 12.16.1
• module version with issue: 1.0.0
• last module version without issue: unknown
• environment (e.g. node, browser, native): https://hapi.dev, and local browser
• used with (e.g. hapi application, another framework, standalone, ...): standalone
• any other relevant information:
  • this happens on your production site (https://hapi.dev) and I can reproduce it building master on this repo.
  • I have tried this with Firefox 75.0b10 (developer edition) and Safari (13.0.5) both on MacOS (10.15.3)

What are you trying to achieve or the steps to reproduce?

In the module help, (for example https://hapi.dev/module/joi/api/?v=17.1.1) if you expand a submenu then future mouse clicks are offset vertically, so that when you later try to click something, it actually selects the item a few sections above it.

What was the result you got?

Clicking items selects the wrong thing, I've included this gif capturing the whole experience (http://g.recordit.co/WvMy52Psab.gif):

What result did you expect?

I expected to be able to expand/contract submenu items and continue to be able to precisely pick the document I wanted to see.

This is making working with Joi quite hard! Thanks for all the work so far, please let me know what else I can provide to help solve this issue!

All the best.

Investigate a potential error in Joi api link

Support plan

• is this issue currently blocking your project? (yes/no): no
• is this issue affecting a production system? (yes/no): no

Context

• node version:
• module version with issue:
• last module version without issue:
• environment (e.g. node, browser, native):
• used with (e.g. hapi application, another framework, standalone, ...):
• any other relevant information: someone raised the problem in Slack about the Joi api section raising errors.

What are you trying to achieve or the steps to reproduce?

Here the person's message:

Hey guys, I’m not sure if this is the best forum, but it looks like http://hapi.dev/module/joi/api is currently broken in “production.” I’m assuming the issue is that when Eran moved Joi, it’s 404ing because the code can no longer find this module?

What was the result you got?

Here is a screenshot he provided:

What result did you expect?

No errors. I believe we already handled Joi departure on the website so this might be a regression.

Family TOC doesn't scroll with text

Open https://hapi.dev/family/joi/ and scroll down with TOC open.

Vision API navigation is broken

Context

• node version: v12.13.0
• module version: latest

What are you trying to achieve or the steps to reproduce ?

The markdown used in Vision's API.md file is not being parsed correctly on the hapi.dev site.
See: https://hapi.dev/module/vision/api/ and notice the sidebar nav broken.

The offending markdown seems to be in the following file, I imagine its the link in the header: https://raw.githubusercontent.com/hapijs/vision/master/API.md

## The `view` [handler](https://github.com/hapijs/hapi/blob/master/API.md#serverdecoratetype-property-method-options)

Google analytics

https://github.com/nuxt-community/analytics-module

<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-144917045-1"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'UA-144917045-1');
</script>

Add support policy (page content below)

# **hapi** modules LTS support policy

The hapi core module and its dependencies are published under the following support rules:

TL;DR

Every **major** version of the [core module](https://github.com/hapijs/hapi) receives at least one year of support from the time of publication of the first `x.0.0` release. When a new **major** version is published, the previous **major** version gets at least 3 months of support from that moment. There are typically one to three major releases each year and most are simple to upgrade. Core dependencies are maintained as long as they are used by a supported core version.

## Current versions

The full and up to date list of supported moduled under a free open source license and paid commercial license is available at the [module status page](https://hapi.dev/resources/status/).

## Latest version

The latest version of the `hapi` module published to [npm](https://www.npmjs.com/package/hapi) is the current actively supported version. It receives bug fixes, security patches, and new features on an ongoing basis.

Only the latest published module of the current **major** version is actively supported. For example, if the current published version is `v10.2.3`, it is the only supported version of the `v10.x.x` branch. If you are using an older version of `v10.x.x` such as `v10.0.4`, you must upgrade to `v10.2.3` before opening issues and seeking support.

## Previous **major** version

Once a new major version is published, the previous major version goes into LTS maintenance mode. Versions in maintenance mode receive critical bug fixes and security patches but do not receive new features.

Each major version branch stays in maintenance mode for whichever is the **longer** period:
- 1 year from the day of the first publication of **this** major version, or
- 3 months from the day of the first publication of the **following** major version.

For example, if:
- version `v9.0.0` was published on January 1st, 2010, and
- version `v10.0.0` was published on May 1st, 2010

Support for `v9.x.x` will end on January 1st, 2011 (one year from time of initial publication of
the `v9.0.0` release).

However, if:
- version `v9.0.0` was published on January 1st, 2010, and
- version `v10.0.0` was published on December 1st, 2010

Support for `v9.x.x` will end on March 1st, 2011 (three months from time of initial publication of
the `v10.0.0` release).

## Deprecated versions

When a version is no longer supported, it will be marked as `deprecated` in the npm registry. You
may continue using it at your own risk, ignoring the warning messages.

## Commercial support

Every module used by hapi v16 or newer has a maintained LTS version available under a commercial license. For more information, visit the [support page](https://hapi.dev/support).

Schema Tester Webpage not working

Support plan

• which support plan is this issue covered by? (e.g. Community, Core, Plus, or Enterprise): Community
• is this issue currently blocking your project? (yes/no): no
• is this issue affecting a production system? (yes/no): no

Context

• node version: none
• module version: latest
• environment (e.g. node, browser, native): browser
• used with (e.g. hapi application, another framework, standalone, ...): nothing
• any other relevant information: hapi.dev website

How can we help?

Hi, I really liked the online Schema Validator page at https://hapi.dev/module/joi/tester/. However the page does not load lately. The errors displayed in the console are

SyntaxError: invalid regexp group 2 da2434fe4ea5ef609506.js:1:1
ChunkLoadError: "Loading chunk 25 failed.
(missing: https://hapi.dev/_nuxt/da2434fe4ea5ef609506.js)"
    NuxtJS 55
ab3bd582bb5dd98bcefc.js:2:161133

I tried the page on multiple devices and browsers, but got always the same result. Is this error known?

Documentation headers lack `id` attribute

Support plan

• which support plan is this issue covered by? (e.g. Community, Core, Plus, or Enterprise): Community
• is this issue currently blocking your project? (yes/no): no
• is this issue affecting a production system? (yes/no): no

Context

• node version: v13.11.0 (irrelevant, though)
• module version with issue: Commit 2dee2b6 (hapi.dev has no release numbers listed in GitHub)
• last module version without issue: Don't know (see below)
• environment (e.g. node, browser, native): browser
• used with (e.g. hapi application, another framework, standalone, ...): standalone
• any other relevant information:

I clicked back through some very old commits (such as cdc0a5d) in an attempt to binary search for the start of the problem and noticed a few things:

1. Older versions of the documentation had a table of contents at the top that was removed at some point (possibly because it didn't work?)
2. Documentation is generated from Markdown files, so whatever tool is performing the generation is failing to place the id attribute
3. All of the headers possessed a starting <a> tag before the actual header name -- this could be what's tripping up the Markdown generation? (just a thought, can't say for certain)

What are you trying to achieve or the steps to reproduce?

// No relevant code (code block left in case a template scanning bot would otherwise invalidate my bug report)

I'm attempting to copy a section link from the hapi.dev documentation to share with my team, using this icon:

What was the result you got?

The following link was copied to my clipboard:

https://hapi.dev/tutorials/auth/?lang=en_US#

Directing someone to this link loads the page but does not scroll to the appropriate section

What result did you expect?

A link similar to the following:

https://hapi.dev/tutorials/auth/?lang=en_US#basic

When such a link is clicked, I would expect it to load the page and scroll to the appropriate section

Hapi.dev seems to only be serving docs for v20

Context

• node version: 10
• module version: 18

What are you trying to achieve or the steps to reproduce ?

Hapi.dev seems to only be serving docs for v20.

Visiting /api/?v=18.4.1 redirects to /api/?v=20.0.0, and the UI only offers v20 to choose.

Is this intentional?

Thank you.

In the labs API documentation, reorganize `script.test` to make Flags subsection more apparent?

Context

https://hapi.dev/family/lab/?v=22.0.2

• node version: N/A (issue pertains to formatting of documentation at hapi.dev)
• module version: 22.0.2

What are you trying to achieve or the steps to reproduce ?

First off, apologies if this issue is better filed directly on the labs repo. I filed here because I observed the issue on the site; happy to relocate this issue if you believe it's relevant.

On reading through the lab documentation the other day, I found it a bit unexpected that the "Flags" subsection appears nested under script.test.skip, given that flags are used by all variants of the script.test method (e.g. plain, skip, and only). Do y'all think it would be beneficial to somehow relocate the flags section to make that feature more apparent?

A couple of ideas:

• Move the "Flags" subsection to the same header level as the other children of the "Methods" section i.e. on the same level as script.test.skip, instead of nested within it

• Make script.test its own section; nest script.test.only, script.test.skip, and Flags under script.test

So, the docs would look like:

-- script.test
    |-- Flags
    |-- only()
    |-- skip()

To be clear, not a big deal at all, of course, just something that for whatever reason didn't sync with my brain :)
Thanks for all the hard work on the site and on this great community in general! Viva hapi!

Update Slack invite link

The Slack invite link has expired.

Add Netlify badge

https://www.netlify.com/press/#badges

Add Dark Badge to the bottom of the home page.

Infinite redirects from `https://hapi.dev/api/` to `https://hapi.dev/api/`

When I try to access https://hapi.dev/api/ I get 301 redirects to the same URL in a loop forever until Chrome stops trying.

Support multiple versions of family docs

Similar to hapi's multiple versions. The list of versions should be based on branches starting with a v and number (e.g. v14*) and use the version in the package.json file of the branch.

Add "copy to clipboard" feature to code examples

Support plan

• which support plan is this issue covered by? (e.g. Community, Core, Plus, or Enterprise):
  Community
• is this issue currently blocking your project? (yes/no):
  no
• is this issue affecting a production system? (yes/no):
  no

Context

• node version:
• module version:
• environment (e.g. node, browser, native):
• used with (e.g. hapi application, another framework, standalone, ...):
• any other relevant information:

What problem are you trying to solve?

Someone on the Slack channel asked if we could add a "copy to clipboard" feature to code examples on the website. Jarrod and I agreed it would be a good addition so I'll do it.

As Jarrod mentioned on Slack:

There is a similar feature in the API section where you can copy the address to the section you are looking at.

Let's see if we can reuse the same stuff for that purpose or we could also use something like: https://clipboardjs.com/.

Do you have a new or modified API suggestion to solve the problem?

Remove extra Github API calls in tutorial languages selection

Support plan

• is this issue currently blocking your project? (yes/no):
• is this issue affecting a production system? (yes/no):

Context

• node version:
• module version with issue:
• last module version without issue:
• environment (e.g. node, browser, native):
• used with (e.g. hapi application, another framework, standalone, ...):
• any other relevant information:

What are you trying to achieve or the steps to reproduce?

const some = 'properly formatted code example';

What was the result you got?

What result did you expect?

Routing tutorial recommends using encodeURIComponent for HTML

In the Routing tutorial, encodeURIComponent is used 6 times (including two typos of encodeURLComponent) to escape HTML. This is wrong because it replaces characters with percent-encoding (for example, space is replaced with %20), which won't be displayed correctly as HTML.

There are two ways to fix this:

1. Remove encodeURIComponent and set Content-Type to text/plain. So the first example would become:

   return h.response(`Hello ${request.params.user}!`).type('text/plain');
   

2. Recommend Hoek.escapeHtml instead. So the first example would become:

   return `Hello ${Hoek.escapeHtml(request.params.user)}!`;
   

I don't know which one is better for a tutorial about routing, so I opened this issue instead of submitting a PR.

Documentation links for many modules are broken

Context

• node version: 12.18.2
• module version: 19.1.1

What are you trying to achieve or the steps to reproduce ?

The documentation links for many modules are broken. For example: https://hapi.dev/module/joi is 404 now, together with many others.

ERR_FAILED https://hapi.dev/

https://hapi.dev/ website couldn't be opened.

Uncaught (in promise) no-response: no-response :: [{"url":"https://hapi.dev/"}]
    at a.makeRequest (https://cdn.jsdelivr.net/npm/[email protected]/workbox/workbox-strategies.prod.js:1:2145)

Context

Latest Chrome and FF

What are you trying to achieve or the steps to reproduce?

Open https://hapi.dev/

What was the result you got?

Working website.

What result did you expect?

ERR_FAILED

[docs] Add diagram to "Lifecycle methods" section

Support plan

Community

• is this issue currently blocking your project? (yes/no): no
• is this issue affecting a production system? (yes/no): no

Context

• node version: irrelevant
• module version: 20
• environment (e.g. node, browser, native): irrelevant
• used with (e.g. hapi application, another framework, standalone, ...): irrelevant
• any other relevant information: irrelevant

What problem are you trying to solve?

Detailed description of request lifecycle is rather complicated and it's hard to track flow.

Do you have a new or modified API suggestion to solve the problem?

Add flow diagram explaining request lifecycle.

Friendlier UX with simple tab title reversal

Support plan

• is this issue currently blocking your project? (yes/no):no
• is this issue affecting a production system? (yes/no):no

Context

• node version: any
• module version: any
• environment (e.g. node, browser, native): browser
• used with (e.g. hapi application, another framework, standalone, ...): hapi application
• any other relevant information: browser tab title format 'hapi.dev - specificPageTitle' makes many tabs opened at once hard to navigate

What problem are you trying to solve?

Many webpage's titles are named like "specific page - broader page(i.e. my search text - google), hapi.dev does this inverse, look at the title, it starts with 'hapi.dev -', that makes many opened hapi.dev tabs hard to navigate as last title part(specific one) is not visible fully, in attached pictures there are four hapi tabs and its impossible to visually see which specific hapi tabs are open in the browser

const some = 'properly formatted code example';

Do you have a new or modified API suggestion to solve the problem?

Just reverse the titles, so its 'testing - hapi.dev" "code v8.0.1 - hapi.dev" not "hapi.dev - testing" "hapi.dev - code v8.0.1"

the https://hapi.dev website is down

Support plan

• which support plan is this issue covered by? (e.g. Community, Core, Plus, or Enterprise):
• is this issue currently blocking your project? (yes/no):
• is this issue affecting a production system? (yes/no):

Context

• node version:
• module version with issue:
• last module version without issue:
• environment (e.g. node, browser, native):
• used with (e.g. hapi application, another framework, standalone, ...):
• any other relevant information:

What are you trying to achieve or the steps to reproduce?

const some = 'properly formatted code example';

What was the result you got?

What result did you expect?

Remove problematic part from default auth strategy in languages other than english

Context

• node version: n/a
• module version: n/a

What are you trying to achieve or the steps to reproduce ?

An issue was raised #459 which was fixed in this MR #460 regarding a mismatch between the documentation and the actual default auth strategy behavior. It was fixed in english but not in the other languages. Before adding the proper translations, we'll just delete the wrong part.

Feature: Print Style

Hi,

is it possible to fix the print style on hapi.dev to not include the sidebar and display only the content for API, Style Guide, etc.?

Best regards,
Janos

Open API TOC to right place when using link with anchor

For example: https://hapi.dev/api/#route.options.payload.parse

Remove commercial support text

We should remove references to commercial support, since that will be traveling with Eran and no longer officially supported by hapi itself given hapijs/hapi#4113. Eran has offered to go over any of these website changes together.

Documented code to set cookie gives 500 error

Context

• node version: 12.14.1
• module version: ^19.1.1

What are you trying to achieve or the steps to reproduce ?

I'm very new to hapi and just testing it a bit. I'm following the "setting a cookie" section of the express migration guide and copied the given code:

const Hapi = require('@hapi/hapi');

const server = Hapi.server({ port: 8000 });

server.state('data', {
    ttl: null,
    isSecure: true,
    isHttpOnly: true
});

server.route({
    method: 'GET',
    path: '/',
    handler: function (request, h) {

        h.state('data', {username: 'tom'});
        return h.response('Hello');
    }
});

I added server.start() and sent a request to the server. This results in a 500 error:

Debug: internal, implementation, error 
    Error: Invalid cookie value: [object Object]

I found that adding encoding: 'base64json' to the cookie options makes it work again but as a complete beginner I expected the documented code to work out of the box.

Fix API TOC sub headings

scheme should be auth.scheme. Only remove the prefix if it matches the above section title.

Sluggish search on https://hapi.dev/

Support plan

• which support plan is this issue covered by? Core
• is this issue currently blocking your project? no
• is this issue affecting a production system? no

Context

• node version: N/A
• module version with issue: N/A
• last module version without issue: N/A
• environment (e.g. node, browser, native): browser
• used with (e.g. hapi application, another framework, standalone, ...): https://hapi.dev/
• any other relevant information:

What are you trying to achieve or the steps to reproduce?

Go to https://hapi.dev/family/joi/api/?v=17.1.0 and use search feature. Ex: try and search for any.validate

What was the result you got?

Website seemed sluggish when searching for content. Profiling with chrome reveals that the clipboard function was being called multiple times. Also, the clipboard icon duplicated on keydown.

What result did you expect?

Speedy search

update proper link for gist code sample

Url: https://hapi.dev/resources
section : Gists and code samples
issue: code sample repo links are not working it leads to 404 in github, Kindly update proper links or remove that section.

joi has been replaced by @hapi/validate

Context

• node version: lts
• module version: all

What are you trying to achieve or the steps to reproduce ?

please update docs, when to update?

Fix security dependency warnings

Wither hawk?

Support plan

• is this issue currently blocking your project? (yes/no): yes
• is this issue affecting a production system? (yes/no): yes

Context

• node version: 12
• module version: 8.0
• environment (e.g. node, browser, native): node + browser
• used with (e.g. hapi application, another framework, standalone, ...): express
• any other relevant information: none

How can we help?

We use Hawk for authentication. https://www.npmjs.com/package/@hapi/hawk appears to be the latest release, but there is no changelog in the repository. The README's changelog links to nowhere. I don't see the library listed under https://hapi.dev/module/?sort=name. Has this been de-supported? What changes occurred between v7 and v8? What is the recommendation for users of this library?

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper 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 it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

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

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Copy link to clipboard functionality is broken

Support plan

• which support plan is this issue covered by? (e.g. Community, Core, Plus, or Enterprise): Community
• is this issue currently blocking your project? (yes/no): No
• is this issue affecting a production system? (yes/no): No

Context

• node version: N/A
• module version with issue: N/A
• last module version without issue: N/A
• environment (e.g. node, browser, native): Chrome browser
• used with (e.g. hapi application, another framework, standalone, ...): N/A
• any other relevant information: -

What are you trying to achieve or the steps to reproduce?

When trying to use the "Copy link to clipboard functionality", the "undefined" word is copied to the clipboard instead of the expected link.

Have seen it on the site API docs

What was the result you got?

The "undefined" word is copied to clipboard

What result did you expect?

The actual link to the documentation section is copied to clipboard

Slack Link Dead

The Slack Link on the Homepage https://hapi.dev/support/ is dead.

Edit: The link in the footer works though.

Continuously declared headers do not break line

Support plan

• which support plan is this issue covered by? (e.g. Community, Core, Plus, or Enterprise): Community
• is this issue currently blocking your project? (yes/no): No
• is this issue affecting a production system? (yes/no): No

Context

• node version: -
• module version with issue: -
• last module version without issue: -
• environment (e.g. node, browser, native): Chrome browser
• used with (e.g. hapi application, another framework, standalone, ...): -
• any other relevant information: -

What are you trying to achieve or the steps to reproduce?

Whenever there are headers declared one after the other, they are rendered on the same line instead of multiple lines

I think it might be caused because headers are declared with inline-block display, instead of block

What was the result you got?

Continuously declared headers are rendered in the same line

What result did you expect?

Continuously declared headers are rendered in different lines

Usage of qs in routing tutorial does not work

Context

https://hapi.dev/tutorials/routing/?lang=en_US#query

• node version: NA
• module version: https://hapi.dev/tutorials/routing/?lang=en_US#query

What are you trying to achieve or the steps to reproduce ?

It seems like the documentation for using qs when dealing with complex query parameters might be wrong. The documentation has this:

const Hapi = require('@hapi/hapi');
const Qs = require('qs');

const server = Hapi.server({
    port: 3000,
    host: 'localhost',
    query: {
        parser: (query) => Qs.parse(query)
    }
});
...

Unsurprisingly, I discovered this didn't work as Qs.parse expects a string and from my understanding of hapi, request.query should be an Object See .

Am I missing some details?

Modules search functionality doesn't work

Support plan

• which support plan is this issue covered by? (e.g. Community, Core, Plus, or Enterprise): Community
• is this issue currently blocking your project? (yes/no): No
• is this issue affecting a production system? (yes/no): No

Context

• node version: None
• module version with issue: None
• last module version without issue: None
• environment (e.g. node, browser, native): Browser (Chrome or Firefox)
• used with (e.g. hapi application, another framework, standalone, ...): Hapi site
• any other relevant information: None

What are you trying to achieve or the steps to reproduce?

When trying to use the "Search modules" functionality at the Modules page nothing happens after using "Enter" or clicking on the "lens" icon

What was the result you got?

Nothing happens

What result did you expect?

The entered search term would filter the module list on the right.

Fix carbon ads and nuxt target 'static'

Support plan

• is this issue currently blocking your project? (yes/no):
• is this issue affecting a production system? (yes/no):

Context

• node version:
• module version with issue:
• last module version without issue:
• environment (e.g. node, browser, native):
• used with (e.g. hapi application, another framework, standalone, ...):
• any other relevant information:

What are you trying to achieve or the steps to reproduce?

const some = 'properly formatted code example';

What was the result you got?

When building the website using target: 'static' in nuxt.config.js the carbon ads script tag is not added to the DOM hence ads are not showing up.

What result did you expect?

Ads should be displayed. We've removed the target: 'static' for now (#438)

Perhaps the problem comes from the mounted lifecycle which is not triggered when generating the website statically.