Releases · poppinss/hooks

The providers were tracked separately from the hooks and therefore their order of execution will always be at the last or the first. It can be mixed with hooks. For example:

hooks.add('saving', () => {
  console.log('first')
})

class SomeProvider {
  saving() {
    console.log('saving')
  }
}
hooks.provider(SomeProvider)

hooks.add('saving', () => {
  console.log('third')
})

The execution output will be

first
third
second

This can be problematic in some edge case scenarios and we want to guarantee the order of execution to be same as the order of defining hooks or providers. Therefore, the providers have been removed

Removing executors

Custom executors were meant to customize how a hook handler should be called. The same can be achieved using object based hooks and wrapping the original hook handler.

Commits

refactor: remove providers and executor in favor of object based hooks b756e70

v7.0.0-0...v7.1.0-0

Assets 2

01 Nov 06:11

thetutlage

v7.0.0-0

17cfafa

Rewrite in ESM and refactoring internals Pre-release

Pre-release

This release sits on the last major pre-release and has following breaking changes on top of it.

The main export now uses the default export to export the Hooks class. Earlier it was a named export.

The types are moved to a separate subpath export.

// Earlier
import type { HooksHandler } from '@poppinss/hooks'

// Now
import type { HooksHandler } from '@poppinss/hooks/types'

The Hooks class now allows defining types for the known events well in advance. This makes the class and the underlying methods type safe. As a result, some of the types like HooksHandler needs generics to know the type of the arguments
The hooks.runner method does not accept the 2nd argument for ignoring hooks by name. Instead, you should call the runner.without method.
```
// Earlier
hooks.runner('creating', ['hashPassword']).run()

// Now
hooks.runner('creating').without(['hashPassword']).run()
```