feat!: replace static class properties with an exported as-const events object

[untemps]

Summary

⚠️ Breaking change

Replace the static class properties (DOMObserver.ADD, DOMObserver.EXIST, etc.) with a standalone exported as const object. This removes the need to import the class just to access event name constants, improves tree-shaking, and enables better TypeScript inference.

Current state

// Must import the class even if only using constants
import { DOMObserver } from '@untemps/dom-observer'

obs.watch('#foo', cb, { events: [DOMObserver.ADD, DOMObserver.REMOVE] })

The constants live on the class:

class DOMObserver {
    static EXIST  = 'DOMObserver_exist'
    static ADD    = 'DOMObserver_add'
    static REMOVE = 'DOMObserver_remove'
    static CHANGE = 'DOMObserver_change'
    static EVENTS = [...]
}

Proposed API

// New top-level export
export const DOMObserverEvent = {
    EXIST:  'DOMObserver_exist',
    ADD:    'DOMObserver_add',
    REMOVE: 'DOMObserver_remove',
    CHANGE: 'DOMObserver_change',
} as const

export const DOMObserverEvents = Object.values(DOMObserverEvent) as DOMObserverEventValue[]

export type DOMObserverEventValue = typeof DOMObserverEvent[keyof typeof DOMObserverEvent]

Usage:

import { DOMObserver, DOMObserverEvent } from '@untemps/dom-observer'

obs.watch('#foo', cb, {
    events: [DOMObserverEvent.ADD, DOMObserverEvent.REMOVE],
})

Benefits

1. Tree-shaking — bundlers can eliminate DOMObserver class code when only constants are needed (e.g. in type-checking files or test utilities).
2. No class instantiation required — constants are usable without new DOMObserver() or even referencing the class.
3. Better TypeScript narrowing — as const values produce literal types directly; static class properties require typeof DOMObserver.ADD for the same effect.
4. Conventional — aligns with the pattern used by most modern TypeScript libraries (Zod, TanStack, etc.).

Breaking changes

Before	After
DOMObserver.ADD	DOMObserverEvent.ADD
DOMObserver.EXIST	DOMObserverEvent.EXIST
DOMObserver.REMOVE	DOMObserverEvent.REMOVE
DOMObserver.CHANGE	DOMObserverEvent.CHANGE
DOMObserver.EVENTS	DOMObserverEvents

Migration

A simple global find-and-replace handles the majority of cases. The static properties could be kept as deprecated aliases for one major version to ease migration.

Note on naming conflict

The existing exported type DOMObserverEvent (the union of four string literals) would be renamed — e.g. to DOMObserverEventValue or DOMObserverEventType — to free the name for the as const object. This is an additional (small) breaking change to the type export.

[untemps]

🎉 This issue has been resolved in version 5.0.0-beta.5 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀