When I run the package it suddenly appears that:

node_modules/@adminjs/hapi/src/extensions/session-auth.ts:49:18 - error TS2322: Type '{ 'hapi-auth-cookie': { redirectTo: false; }; }' is not assignable to type 'PluginSpecificConfiguration'.
  Object literal may only specify known properties, and ''hapi-auth-cookie'' does not exist in type 'PluginSpecificConfiguration'.

49       plugins: { 'hapi-auth-cookie': { redirectTo: false } },
                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

node_modules/@adminjs/hapi/src/plugin.ts:156:15 - error TS18046: 'e' is of type 'unknown'.

156           if (e.statusCode >= 400 && e.statusCode < 500) {
                  ~

node_modules/@adminjs/hapi/src/plugin.ts:156:38 - error TS18046: 'e' is of type 'unknown'.

156           if (e.statusCode >= 400 && e.statusCode < 500) {
                                         ~

node_modules/@adminjs/hapi/src/plugin.ts:157:32 - error TS2345: Argument of type 'unknown' is not assignable to parameter of type 'Error'.

157             throw Boom.boomify(e, { statusCode: e.statusCode });
                                   ~

node_modules/@adminjs/hapi/src/plugin.ts:157:49 - error TS18046: 'e' is of type 'unknown'.

157             throw Boom.boomify(e, { statusCode: e.statusCode });
                                                    ~

node_modules/@adminjs/hapi/src/plugin.ts:161:32 - error TS2345: Argument of type 'unknown' is not assignable to parameter of type 'Error'.

161             throw Boom.boomify(e);

Even though I replace depreciated hapi-auth-cookie with @hapi/cookie, it still doesn't work.

Is there anything to resolve it?

When in hapi server configuration I added option:
const server = new Hatpi.Server({ routes: { files: { relativeTo: Path.join(__dirname, 'assets') //<- This is important line! } } });
https://github.com/SoftwareBrothers/admin-bro-hapijs/blob/a56cbc43bc90ccec6c023ef71ad32e719d5e4909/plugin.js#L136 This is probably related to this line. Src is relating on default relativeTo value which is '.' so any change to it throws 403 Forbidden.

Here is documentation to routes/files option https://github.com/hapijs/hapi/blob/master/API.md#route.options.files
Also possible fix could be to play with confine in Inert library: https://github.com/hapijs/inert

Getting the following error.

Error: Cannot find module 'admin-bro'
Require stack:
- /Users/admin-bro-test/node_modules/admin-bro-hapijs/plugin.js
- /Users/admin-bro-test/node_modules/admin-bro-hapijs/index.js
- /Users/admin-bro-test/server/manifest.js
- /Users/admin-bro-test/server/index.js

Following module added. "admin-bro-hapijs": "^2.0.0",

Will debug this further during this weekend and provide my findings.

How to use admin-bro-hapijs with sequelizejs adapter admin-bro-sequelizejs?

It would be nice to have it in the documentation.

Hi,

Almost all hapi packages are deprecated in favor of @hapi/*

hapi -> @hapi/hapi

Affected: hapi, boom, hapi-auth-cookie, and inert.

Hi,

There are the same packages inert and hapi-auth-cookie in the dependencies and peerDependencies. As i know it is pointless.

Is this package abandoned?

🚨 The automated release from the beta 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 beta 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.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀