Skip to content

Plugin schema too restrictive #2822

Closed
Closed
@ldesplat

Description

@ldesplat

Hi,

Since Hapi 10.2 or earlier, Hapi decided to check the schema of everything that a plugin exports. Most likely due to the new features.

This breaks the Bell plugin since hapijs/bell#48 . Now, I don't mind too much just having those Utilties being provided from server.expose since Bell is meant to be used with Hapi. But, before I make any of those breaking changes I was wondering if this is intentional and if there is a plan to allow plugins to just expose plain utilities that way.

Thank you!

// this now breaks in Hapi 10
exports.providers = Providers;
exports.oauth = OAuth;

exports.register = ...

exports.register.attributes = ...

Metadata

Metadata

Assignees

Labels

bugBug or defect

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions